[Breaking] PyPi publish changes - unleash the Poetry!

[osfanbuff63]

Whew, here's a quick summary of all the breaking changes...

• Source directory is now vanilla_installer instead of vanilla-installer (Mentioned on Discord in an internal channel)
• Dependency management has been completely migrated to poetry
  • envs/ no longer exists, as it's unneeded
  • It's much easier to manage more than 1 Python version...
  • ...as it utilizes the pyproject.toml, using Poetry's expansions which allows a rule such as >=3.8,<=3.11.
• To install the GUI, you must install it with the gui extra
• Dependencies for docs have been split into the docs group, and development dependencies in the dev group
  • These can be installed with poetry install --with <group>. Source from Poetry's docs
• You can no longer run the program using python cli.py or python gui.py
  • This is due to requirements for packaging. When you run poetry install, it installs the current project as well, as long as you do not specify --no-root. This allows for the program to be run as vanilla-installer as long as you have the venv checked out.
• Probably more but I'm tired and don't have time to write a longer PR description 😅

This is majorly for #21, but using poetry instead of pipenv if we're going to publish is a convenience thing, as it uses pyproject.toml.

[Kichura]

The GitHub Actions script is giving alerts about sensitive data being included, You reckon to investigate that?

[osfanbuff63]

Looks like it's upstream, will investigate more tomorrow.

[osfanbuff63]

Confirmed it's an upstream issue with CodeQL not liking requests. It was only finding it in venv code though, so this may or may not be relevant. Surprising that it only shows up now though.

[Kichura]

Very good although some questions are yet to be asked.

[nsde]

Is this ready to be merged?

[osfanbuff63]

If you think so, I think this could be ready, after all saves some merge conflicts later lol