Re: django-pipeline / slimit
On Wed, 23 Mar 2016, Brian May wrote: > I: pybuild base:184: PYTHONPATH=. python3.5 /usr/bin/django-admin test > --settings=tests.settings ^ > File "/«PKGBUILDDIR»/pipeline/compressors/slimit.py", line 12, in > compress_js > from slimit import minify > ImportError: No module named 'slimit' [...] > Does this mean we need to change the slimit package into python-slimit > and python3-slimit packages? Looks like so, indeed. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
Re: django-pipeline / slimit
Raphael Hertzog writes: > On Wed, 23 Mar 2016, Brian May wrote: >> I: pybuild base:184: PYTHONPATH=. python3.5 /usr/bin/django-admin test >> --settings=tests.settings > ^ >> File "/«PKGBUILDDIR»/pipeline/compressors/slimit.py", line 12, in >> compress_js >> from slimit import minify >> ImportError: No module named 'slimit' > [...] >> Does this mean we need to change the slimit package into python-slimit >> and python3-slimit packages? > > Looks like so, indeed. Just noticed there is already an bug open on this, filled by me over a year ago. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779321 Looks like slimit doesn't support Python3 and hasn't had an upstream release since 2013-03-26. Any suggestions where to go from here? Maybe hack pipeline to disable the failing test? I think pipeline can be configured to use jsmin instead of slimit and jsmin is packaged in python2 and python3 versions. -- Brian May
Re: django-pipeline / slimit
On Wed, 23 Mar 2016, Brian May wrote: > Looks like slimit doesn't support Python3 and hasn't had an upstream > release since 2013-03-26. > > Any suggestions where to go from here? > > Maybe hack pipeline to disable the failing test? I think pipeline can be > configured to use jsmin instead of slimit and jsmin is packaged in > python2 and python3 versions. Yeah, skip the test on Python 3, tell upstream that slimit is not supported on Python 3 and that the test should be skipped there. Make sure that slimit is not the default. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
Re: Handling python modules collision
Thanks Dmitry and Scott, this is very informative, I missed the key point for "Conflicts". I opened a discussion about renaming miguelgrinberg/python-socketio, let's see what it gives. Thank you, Fred
Re: django-pipeline / slimit
Raphael Hertzog writes: > Yeah, skip the test on Python 3, tell upstream that slimit is not > supported on Python 3 and that the test should be skipped there. Done. https://github.com/jazzband/django-pipeline/issues/554 > Make sure that slimit is not the default. It wasn't. However Yuglify was the default. Yuglify isn't in Debian. Or if it is I can't find it. IIRC there were licensing issues. So I have changed the defaults to use cssmin and jsmin. -- Brian May
Bug#819126: ITP: tzlocal -- tzinfo object for the local timezone
Package: wnpp Severity: wishlist Owner: Brian May * Package name: tzlocal Version : 2.1 Upstream Author : Lennart Regebro * URL : https://github.com/regebro/tzlocal * License : CC0 Programming Lang: Python2 and Python3 Description : tzinfo object for the local timezone This module attempts to fix a glaring hole in pytz, that there is no way to get the local timezone information, unless you know the zoneinfo name, and under several Linux distros that’s hard or impossible to figure out. . With tzlocal you only need to call get_localzone() and you will get a tzinfo object with the local time zone info. On some Unices you will still not get to know what the timezone name is, but you don’t need that when you have the tzinfo file. However, if the timezone name is readily available it will be used. . This package contains the Python 2 module. This is required for the latest version of apscheduler. I plan to maintain it as part of the Debian Python Modules Team.
