Version 1.15

[PFython]

I just published Version 1.15 of easyPyPI which I'm quite excited about:

1. The config file now saves your most recent answers, including values that probably won't change much for typical users (Author, Email, Github_ID, Twine credentials etc.).

2. If easyPyPI finds an existing setup.py (created in the easyPyPI format) it uses those values in preference to config file values if there's a conflict.

3. I've restructured the code so that everything is under the Package class and you can now initiate easyPyPI with package = Package(optional_name) which makes it much easier to manually get/set attributes and run the new "Entry Points"

4. I've also refactored my structure into four easy to follow steps, each of which can be called with an "Entry Point" method:

   package.load_defaults()
   package.review()
   package.generate()
   package.upload()
   

5. README, init, script, test, and setup now have template files (in the same directory as easypypi.py) rather than hard-coding them into easypypi.py. This means users can edit or overwrite the template files themselves according to their own standards and preferences.

6. easyPyPI now supports different usernames/passwords for Test PyPI and PyPI, if needed.

7. I've improved the handling of "Cancel" and close window clicks to (mostly) return to the Python interpreter where you can carry on using your package object, but it's not 100% perfect.

In terms of next steps, I really like Ruud's design suggestion for having all fields visible in one (interactive) window rather than clicking through one field at a time BUT when I started trying to implement this I got into a mess... I need to get better with PySimpleGUI to learn two main skills:

• How to dynamically change values when one field is updated e.g. update self.url when self.github_id changes or self.setup_filepath when self.name changes.
• Set checkboxes and radio buttons based on existing values for self.classifiers and self.license_dict respectively.
  For other planned features I'm going to start raising Issues on Github...

Felix asked for permission to Push directly to this repo which I'm happy to do for contributors as an experiment... My slight worry is that with several people all working on this concurrently it might get into a bit of a version control mess. Let's see... if that happens I might have to revert back to Version 1.15 and ask contributors to adopt the more formal process of Fork, Create a new Branch from that Fork (one branch for each new 'idea' or issue/enhancement), then use Pull Requests to keep everyting in sync.

Many thanks for your time and brainpower and I look forward to seeing how this package evolves with new contributions now...