`pypi` projects

[trappitsch]

One of the current limitations is that box cannot use PyApp's self update command, since the installation is always from a local source.
Allowing for virtual projects could allow this to change. The idea here is the following:

• Initialize an empty folder as a virtual box project with all configuration
• Instead of building / using local source, the source can be grabbed from pypi
• Build, package the project with a source from pypi

This way, if the pypi version is updated, executable self update should work.

Why is this cool: Only one box project would need to be created, and could be created directly in a CI workflow upon a new release. However, users with existing programs could self-update.

Another cool thing would be if box could provide a way for a GUI to run through the self-update command on the click of a button...

Some idea, not well thought out yet, but would be nice to keep in mind!

[trappitsch]

Actually, this is all nice and good, however, we should take more of the same approach as the hatch binary builder plugin:

• initialize the project with a flag --pypi (and/or question)
• This adds a some_key = true to the toml file under [tool.box]
• PyApp packaging will not take place with the local binary, but will package from PyPi
• specific PyPi indexes can be set as environmental variables.

A new discussion on variable management can be found in #48