Py2app

-----------

- Make sure the stdout/stderr streams of the main binary of the application
are unbuffered.

See `issue 177 in PyObjC's repository <https://github.com/ronaldoussoren/pyobjc/issues/177/on-python3-print-does-not-automatically>`_ for more information.

- Fix issue 201: py2app is not compatible with pyvenv virtualenvs

With additional fix by Oskari Timperi.

- Fix issue 179: the stdout/stderr streams are no longer forwarded to console.app using ASL (by default),
use "--redirect-stdout-to-asl" to enable the redirection functionality.

Note that for unclear reasons the redirection doesn't work on OSX 10.12 at the moment.

- Fix issue 188: Troubles with lxml.isoschematron

The package 'lxml.isoschematron' is not zip-safe and tries to load resources using the normal
filesystem APIs, which doesn't work when the package is part of a zipfile.

- py2applet now longer uses "argv_emulation" by default, that results in too many problems.

- Issue 174: clean up the summary about missing modules by removing warnings about things that aren't modules.

Also notes when an module is likely an alias for some other module. These changes should remove a lot
of false positive warnings from the output of py2app.

- Fix issue 161: opengl recipe uses "file" function that isn't present on Python 3

- Add "qt5" recipe that does the right thing for the PyQt5 wheel on PyPI (tested with PyQt5 5.6)

- Add support for "loader_path" in the link commands of C extension.

This makes it possible to use wheels that were processed by `delocate-listdeps <https://github.com/matthew-brett/delocate>`_
when building application bundles.

- Do not report imports that are expected to be missing

Patch by Barry Scott.

-----------

- The recipe for virtualenv calls a modulegraph method that was made
private in a recent release and hence no longer worked with py2app 0.9.

Update the recipe to work around this.

----------

- issue 146, 147: The "python" binary in MyApp.app/Contents/MacOS was
the small stub exetable from framework builds, instead of the actual
command-line interpreter. The result is that you couldn't use
``sys.executable`` to start a new interpreter, which (amongst others)
breaks multiprocessing.

- pull request 7: Add support for PyQt5 to the sip recipe. Patch by
Mark Montague.

- pull request 4: Copying PySide plugins was broken due to bad
indentation.

- pull request 5: py2app was broken for python versions that
don't use _sysconfigdata.

- issue 135: Don't sleep for a second after compiling a XIB file

- issue 134: Remove target location before copying files into
the bundle.

- issue 133: Ensure that the application's "Framework" folder
is on the search path for ``ctypes.util.find_library``.

- issue 132: Depend on modulegraph 0.12 to avoid build errors
when the python code contains references to compatibility modules
that contain SyntaxErrors for the current python version.

- Explicitly report modules that cannot be found at the end of
the run (for non-alias builds)

Note: This is just a warning, missing modules are not necessarily
a problem because modulegraph can detect imports for modules that
aren't used on OSX (for example)

- Report modules that contain syntax errors at the end of
the run (for non-alias builds)

Note: This is just a warning, syntax errors be valid when the
dependency tree contains modules for the other major release
of python (e.g a compat_py2 module that contains compatibility
code for Python 2 and contains code that isn't valid Python 3)

------------

- Loading scripts didn't work when --no-chdir was used

Reported by Barry Scott in private mail.

- Fixed argv emulator on OSX 10.9, the way the code detected that the application
was launched through the Finder didn't work on that OSX release.

- The launcher binary is now linked with Cocoa, that should avoid some problems
with sandboxed applications (in particular: standard open panels don't seem
to work properly in a sandboxed application when the main binary is not
linked to AppKit)

- Don't copy Python's Makefile, Setup file and the like into a bundle when
sysconfig and distutils.sysconfig don't need these files (basically, when
using any recent python version).

- Fix some issues with virtualenv support:

* detection of system installs of Python didn't work properly when using
a virtualenv. Because of this py2app did not create a "semi-standalone"
bundle when using a virtualenv created with /usr/bin/python.

* "semi-standalone" bundles created from a virtualenv included more files
when they should (in particular bits of the stdlib)

- Issue 92: Add option '--force-system-tk' which ensures that the _tkinter
extension (used by Tkinter) is linked against the Apple build of Tcl/Tk,
even when it is linked to another framework in Python's std. library.

This will cause a build error when tkinter is linked with a major version of
Tcl/Tk that is not present in /System/Library/Frameworks.

- Issue 80: Add support for copying system plugins into the application
bundle.

Py2app now supports a new option *include_plugins*. The value of this
is a list of paths to plugins that should be copied into the application
bundle.

Items in the list are either paths, or a tuple with the plugin type
and the path::

include_plugins=[
"MyPlugins/MyDocument.qlgenerator",
("SystemConfiguration", "MyPlugins/MyConfig.plugin"),
]

Py2app currently knows about the following plugin suffixes:
``.qlgenerator``, ``.mdimporter``, ``.xpc``, ``.service``,
``.prefPane``, ``.iaplugin`` and ``.action``. These plugins
can be added without specifying the plugin type.

- Issue 83: Setup.py now refuses to install when the current
platform is not Mac OS X.

This makes it clear that the package is only supported on OSX and
avoids confusing errors later on.

- Issue 39: It is now possible to have subpackages on
in the "packages" option of py2app.

- Issue 37: Add recipe for pyEnchant

..note::

The recipe only works for installations of pyEnchant
where pyEnchant is stored in the installation (such
as the binary eggs on PyPI), not for installations
that either use the "PYENCHANT_LIBRARY_PATH" environment
variable or MacPorts.

- Issue 90: Removed the 'email' recipe, but require a new enough version
of modulegraph instead. Because of this py2app now requires modulegraph
0.11 or later.

------------

- Issue 77: the stdout/stderr streams of application and plugin bundles did not
end up in Console.app on OSX 10.8 (as they do on earlier releases of OSX). This
is due to a change in OSX.

With this version the application executable converts writes to the stdout
and stderr streams to the ASL logging subsystem with the options needed to
end up in the default view of Console.app.

NOTE: The stdout and stderr streams of plugin bundles are not redirected, as it
is rather bad form to change the global environment of the host application.

- The i386, x86_64 and intel stub binaries are now compiled with clang on OSX 10.8,
instead of an older version of GCC. The other stub versions still are compiled
on OSX 10.6.

- Issue 111: The site.py generated by py2app now contains a USER_SITE variable
(with a default value of ``None``) because some software tries to import the
value.

- Py2app didn't preserve timestamps for files copied into application bundles,
and this can cause a bytecompiled file to appear older than the corresponding
source file (for packages copied in the bundle using the 'packages' option).

Related to issue 101

- Py2app also didn't copy file permissions for files copied into application
bundles, which isn't a problem in general but did cause binaries to lose
there executable permissions (as noted on Stackoverflow)

- Issue 101: Set "PYTHONDONTWRITEBYTECODE" in the environment before
calling Py_Initialize to ensure that the interpreter won't try to
write bytecode files (which can cause problems when using sandboxed
applications).

- Issue 105: py2app can now create app and plugin bundles when the main script
has an encoding other than ASCII, in particular for Python 3.

- Issue 106: Ensure that the PIL recipe works on Python 3. PIL itself isn't
ported yet, but Pillow does work with Python 3.

- "python setup.py install" now fails unless the machine is running Mac OS X.

I've seen a number of reports of users that try to use py2app on Windows
or Linux to build OSX applications. That doesn't work, py2app now fails
during installation do make this clear.

- Disabled the 'email' recipe for python 3.x as it isn't needed there.

- Issue 91: Added a recipe for `lxml <http://lxml.de/>`, needed because
lxml performs a number of imports from an extension and those cannot
be detected automatically by modulegraph.

- Issue 94: The site-packages zipfile in the application bundle now contains
zipfile entries for directories as well. This is needed to work around
a bug in the zipimporter for Python 3.3: it won't consider 'pkg/foo.py' to be
in namespace package 'pkg' unless there is a zipfile entry for the 'pkg'
folder (or there is a 'pkg/__init__.py' entry).

- Issue 97: Fixes a problem with the pyside and sip recipes when the 'qt_plugins'
option is used for 'image_plugins'.

- Issue 96: py2app should work with python 2.6 again (previous releases didn't
work due to using the sysconfig module introduced in python 2.7)

- Issue 99: appstore requires a number of symlinks in embedded frameworks.

(Version 0.7 already added a link Python.frameworks/Versions/Current, this
versions also adds Python.framework/Python and Python.framework/Resources with
the value required by the appstore upload tool).

- Py2app copied stdlib packages into the app bundle for semi-standalone builds
when they are mentioned in the '--packages' option (either explicitly or
by a recipe). This was unintentional, semi-standlone builds should rely on
the external Python framework for the stdlib.

.. note::

Because of this bug parts of the stdlib of ``/usr/bin/python`` could be
copied into app bundles created with py2app.