The hubstore has its own packaging format, as opposed to standard approach, such as a .whl file with entry_points of setup.py. As a result, you cannot use any of the pre-existing python apps. And if someone makes hubstore-compatible app, it is not going to be usable with regular python tools by default.
The Pyrustic is kinda the same -- it has some cool components, but it also requires a lot of buy-in. I could use better TkInter widgets, but I am not even going to consider it if it requires some sort of interactive, non-scriptable wrapper shell which completely destroys all my existing workflows.
Indeed, Pyrustic is designed in the "all or nothing" fashion because I wanted to make things easier for new Python enthusiasts  and also it's fun to build things from scratch. Then, after my first Show HN, I started to embrace standards: Pyrustic was available exclusively through Github Releases, I then put it on PyPI. Then I moved further away from the standards to offer a packaging/distribution alternative  by taking advantage of Github Releases assets feature and also of the ZIP archive format.
I had planned to implement "requirements.txt" support in Hubstore. Thanks to your feedback I think I can do better. It was fun building solutions from scratch but I'm writing code for humans, I want adoption, so I'm going to do my best to embrace standards even more.
Thanks again for this feedback which I find relevant and useful, I'll be back soon with a version that integrates well with the Python ecosystem, and I'm already looking forward to reading the upcoming HN feedback.
Months ago I showcased  Pyrustic , a framework and software suite to help develop, package, and publish Python desktop applications .
The framework adds megawidgets like Table and Scrollbox to Tkinter, implements views with lifecycle and more GUI related contributions. But it's not just a framework for the GUI, for example it comes with Gurl for resource fetching with a built-in responses caching system and support for conditional requests, multithreading made easier with even the possibility of retrieving from the main thread the values returned by the functions executed in other threads and also the exceptions raised by these functions, etc.
Pyrustic is not a framework highly specialized in a specific domain, but rather a framework which aims to help build full featured desktop applications (capable of resource fetching, database support, etc.)
Pyrustic is also a lightweight software suite: a command line program to help the developer manage his project, a graphical SQL editor, a graphical test runner, and also a tool to publish the packaged application on Github.
Once the developer has published packaged app on Github, the next challenge is: how to make the download-unpack-install-run-manage-apps process easier for the end user ?
So here I am back to showcase Hubstore .
I look forward to reading your comments , questions etc. Thanks for your feedback. Genuinely appreciated.
 https://pyrustic.github.io/ (Pyrustic Demo video)