Adding RC would require updating other scripts to support it. For the
purpose of the changelog just using 4.0.4 should suffice. Might Add
support for this later.
Marking this as an RC as it will take some time for me to get all
packages out and I might need to fix various packaging related bugs.
Will mark as 4.0.4 after all packages exist, should not have application
changes between these two.
Fix the issues with cx_Freeze builds on newer versions of python and
with newer version of PyQt5
- Update .gitignore to ignore .spec files
- Update package.py to use pyInstaller instead of cx_Freeze
- Update requirements-windows to have pyInstaller instead of cx_Freeze
- Update setup.nsi to work with build and packaging changes
- Add win_version_info.temp to build a version information file for
pyInstaller as part of the package.py script
- Update qt/preferences_dialog.py to resize based on layout with fixed
sizing constraints
- Remove _setupUi from qt/se/preferences_dialog.py and just use the
parent class's function
- Remove unused imports from qt/se/preferences_dialog.py
- Update ISSUE_TEMPLATE.md to help obtain better information for bug
reports.
- Update README.md to reflect more recent changes and highlight areas of
need.
* Update setup.nsi
- Always display all language choices to fix#461
- Stop recursively removing installation directory as that
is not a safe operation. This may leave the installation
directory after uninstallation but should be empty. Fix#456.
* Update requirements-windows.txt
- Add pypiwin32 for cx-freeze as it was issuing a warning
- Prevent version 5.1.0 of cx-freeze as it produces non-working
packages for some reason. Version 5.0.2 and 6.0b1 work fine.
* Update setup to delete correct files
Installer will now delete the files in the installation folder along
with the folder if it is empty. Bumped minimum cx-Freeze version to
5.1.1 as files are structured differently in older versions.
Update qtlib to prevent error on multiple calls to close the progress window. I have not been able to duplicate the issue again, to track down the root cause.
Ref #449
These methods were previously called recursively and it seemed to cause
problems in some cases. The recursive nature of these functions not
bringing any notable advantage and `os.walk()` being of better style
anyway, I removed that recursive nature.
Hopefully fixes#421
