Re: django-pipeline / slimit

Brian May writes: > Maybe I should have a look at doing the python-slimit and python3-slimit > split again. Looks like I don't have commit access to PAPT, so I can't commit my changes to SVN. How do I get commit access to PAPT? Thanks -- Brian May

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. Upstream pipeline seem to think slimit works fine with Python 3:

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

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

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",

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

Re: django-pipeline / slimit

Brian May writes: > Ok, so now I think I understand, time to test the lastest version of > pipeline I think. See if that helps. It fixes the problem. However we get a new problem: I: pybuild base:184: PYTHONPATH=. python3.5 /usr/bin/django-admin test