releasenotes.rst 3.6 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182
  1. Release notes
  2. =============
  3. Version 1.6
  4. -----------
  5. * Experimental support for creating installers that :ref:`bundle Python with the
  6. application <python_bundled>`.
  7. Version 1.5
  8. -----------
  9. * New ``exclude`` option to cut unnecessary files out of directories and
  10. packages that are copied into the installer.
  11. * The ``installer.nsi`` script is now built using `Jinja <http://jinja.pocoo.org/>`_
  12. templates instead of a custom templating system. If you have specify a custom
  13. ``nsi_template`` file, you will need to update it to use Jinja syntax.
  14. * GUI applications (running under :program:`pythonw`) have stdout and stderr
  15. written to a log file in ``%APPDATA%``. This should catch all ``print``,
  16. warnings, uncaught errors, and avoid the program freezing if it tries to
  17. print.
  18. * Applications run in a console (under :program:`python`) now show the traceback
  19. for an uncaught error in the console as well as writing it to the log file.
  20. * Install :program:`pynsist` command on Windows.
  21. * Fixed an error message caused by unnecessarily rerunning the installer for the
  22. PEP 397 ``py`` launcher, bundled with Python 2 applications.
  23. * :program:`pynsist` now takes a :option:`--no-makensis` option, which stops it
  24. before running :program:`makensis` for debugging.
  25. Version 1.0
  26. -----------
  27. * New ``extra_preamble`` option to specify a snippet of Python code to run
  28. before your main application.
  29. * Packages used in the specified entry points no longer need to be listed
  30. under the Include section; they are automatically included.
  31. * Write the crash log to a file in ``%APPDATA%``, not in the installation
  32. directory - on modern Windows, the application can't normally write to its
  33. install directory.
  34. * Added an example application using pygtk.
  35. * :doc:`installers` documentation added.
  36. * Install Python into ``Program Files\Common Files`` or ``Program Files (x86)\Common Files``,
  37. so that if both 32- and 64-bit Pythons of the same version are installed,
  38. neither replaces the other.
  39. * When using 64-bit Python, the application files now go in ``Program Files`` by
  40. default instead of ``Program Files (x86)``.
  41. * Fixed a bug in finding the NSIS install directory on 64-bit Windows.
  42. * Fixed a bug that prevented using multiprocessing in installed applications.
  43. * Fixed a bug where the ``py.exe`` launcher was not included if you built a
  44. Python 2 installer using Python 3.
  45. * Better error messages for some invalid input.
  46. Version 0.3
  47. -----------
  48. * Extra files can now be installed into locations other than the installation
  49. directory.
  50. * Shortcuts can have non-Python commands, e.g. to create a start menu shortcut
  51. to a help file.
  52. * The Python API has been cleaned up, and there is some :doc:`documentation
  53. <api/index>` for it.
  54. * Better support for modern versions of Windows:
  55. * Uninstall shortcuts correctly on Windows Vista and above.
  56. * Byte compile Python modules at installation, because the ``.pyc`` files
  57. can't be written when the application runs.
  58. * The Python installers are now downloaded over HTTPS instead of using GPG to
  59. validate them.
  60. * Shortcuts now launch the application with the working directory set to the
  61. user's home directory, not the application location.
  62. Version 0.2
  63. -----------
  64. * Python 2 support, thanks to `Johannes Baiter <https://github.com/jbaiter>`_.
  65. * Ability to define multiple shortcuts for one application.
  66. * Validate config files to produce more helpful errors, thanks to
  67. `Tom Wallroth <https://github.com/devsnd>`_.
  68. * Errors starting the application, such as missing libraries, are now written
  69. to a log file in the application directory, so you can work out what
  70. happened.