Date: Wed, 23 Oct 2013 04:30:02 GMT From: Kubilay Kocak <koobs.freebsd@gmail.com> To: freebsd-python@FreeBSD.org Subject: Re: ports/182332: python packages install packed eggs which makes them unusable for running services Message-ID: <201310230430.r9N4U2vs005572@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/182332; it has been noted by GNATS. From: Kubilay Kocak <koobs.freebsd@gmail.com> To: bug-followup@FreeBSD.org, arcade@b1t.name, python@FreeBSD.org Cc: Subject: Re: ports/182332: python packages install packed eggs which makes them unusable for running services Date: Wed, 23 Oct 2013 15:23:04 +1100 Hi Volodymyr, While it is a desirable (and planned) long-terms goal to have consistent behaviour in the ports tree, there is not *yet* a formal or specific documented policy regarding Python module packaging in FreeBSD. A number of maintainers *do* however, make changes to upstream modules by explicitly setting zip_safe=False in setup.py, or overriding the use of setuptools with plain-old distutils, resulting in the module being installed uncompressed. For those modules or ports that *dont* currently do this such as www/trac, the end-user *can* use the PYTHON_EGG_CACHE environment variable that points to a writable area of the filesystem to address the behaviour. In short, I recommend that this PR be changed, assigning it to the maintainer of the www/trac port for follow-up and resolution.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201310230430.r9N4U2vs005572>