On 27 June 2014 16:50, Raphael Hertzog hert...@debian.org wrote:
Please skip the delayed waiting. It will have to go through NEW anyway.
Have now moved this to DELAYED/0.
--
Brian May br...@microcomaustralia.com.au
Hi,
On Fri, 27 Jun 2014, Brian May wrote:
On 26 June 2014 11:40, Brian May br...@microcomaustralia.com.au wrote:
I committed a working version to subversion.
I just uploaded this to DELAYED/10.
Please skip the delayed waiting. It will have to go through NEW anyway.
Did you manage to
On 27 June 2014 16:50, Raphael Hertzog hert...@debian.org wrote:
Please skip the delayed waiting. It will have to go through NEW anyway.
Will do so when I get the chance.
Did you manage to get it working on wheezy too? I want to continue to
update the backport package so it would be nice
On 26 June 2014 11:40, Brian May br...@microcomaustralia.com.au wrote:
I committed a working version to subversion.
I just uploaded this to DELAYED/10.
Hope everyone is happy with this, if not, should be possible to
cancel/replace it.
--
Brian May br...@microcomaustralia.com.au
On Wed, 25 Jun 2014, Brian May wrote:
If possible we should move them to under /usr/share and eliminate
the image-file-in-usr-lib lintian warning.
Right.
However, this is going to get rather tedious rather quickly. There are
numerous locale directories for example. Think each one has to be
On 25 June 2014 16:27, Raphael Hertzog hert...@debian.org wrote:
Not tested, but you get the idea I guess. And obviously we need strong (=
${binary:Version}) dependency between python*-django and
python-django-common.
# find -type f debian/python3-django/usr/lib/python3/dist-packages/ -not
On 26 June 2014 10:36, Brian May br...@microcomaustralia.com.au wrote:
On 25 June 2014 16:27, Raphael Hertzog hert...@debian.org wrote:
Not tested, but you get the idea I guess. And obviously we need strong (=
${binary:Version}) dependency between python*-django and
python-django-common.
Hello Brian,
thanks for your work!
On Tue, 24 Jun 2014, Brian May wrote:
New patch attached.
/etc/bash_completion.d/django_bash_completion and /usr/bin/django-admin now
supplied with python3-django.
python-django recommends python3-django as a result.
Hopefully I have set the
On 24 Jun 2014 16:51, Raphael Hertzog hert...@debian.org wrote:
It doesn't look clean to have python-django recommends python3-django just
to have django-admin and django_bash_completion. I believe it would better
to move them to a python-django-common package, no?
I can't see how that would
On Tue, 24 Jun 2014, Brian May wrote:
On 24 Jun 2014 16:51, Raphael Hertzog hert...@debian.org wrote:
It doesn't look clean to have python-django recommends python3-django just
to have django-admin and django_bash_completion. I believe it would better
to move them to a python-django-common
On 24 June 2014 16:51, Raphael Hertzog hert...@debian.org wrote:
It doesn't look clean to have python-django recommends python3-django just
to have django-admin and django_bash_completion. I believe it would better
to move them to a python-django-common package, no?
Have done this, result is
New patch attached.
/etc/bash_completion.d/django_bash_completion and /usr/bin/django-admin now
supplied with python3-django.
python-django recommends python3-django as a result.
Hopefully I have set the Breaks/Replaces headers correctly to allow for
upgrades.
Any objections if I commit this
Latest patch attached. As far as I can tell, I now have working packages.
Some generally observations.
* python2: binaries under library path have '#!/usr/bin/env python'.
* python3: binaries under library path have '#!/usr/bin/env python'.
* binaries installed under /usr/bin/ have correct hash
On 18 June 2014 10:11, Brian May br...@microcomaustralia.com.au wrote:
I started work on this, unfortunately, I appear to have got a test
failure. Can't tell if it is python2.7 or python3, my history doesn't go
back far enough:
This test failure only happens on my development box, not a
(CCing Barry who expressed interested in python3-django as well)
Hi,
On Tue, 17 Jun 2014, Brian May wrote:
What needs to happen in order to make this happen? Are there any missing
dependencies?
Django has very few dependencies, so I don't think this is what is
missing. It's just a matter of
On Jun 17, 2014, at 08:52 AM, Raphael Hertzog wrote:
(CCing Barry who expressed interested in python3-django as well)
I started a *very* minimal branch for adding Python 3 packaging to
python-django 1.6, although 1.6.5 is the latest on PyPI (and in Debian).
There's really not much to my branch
I started work on this, unfortunately, I appear to have got a test failure.
Can't tell if it is python2.7 or python3, my history doesn't go back far
enough:
==
FAIL: test_template_loader_postmortem_notreadable
On 18 June 2014 10:11, Brian May br...@microcomaustralia.com.au wrote:
I started work on this, unfortunately, I appear to have got a test
failure. Can't tell if it is python2.7 or python3, my history doesn't go
back far enough:
I tried that again, and this time it works. Weird.
This version
Hello,
I would second this request
What needs to happen in order to make this happen? Are there any missing
dependencies?
Can we offer any assistance?
Thanks.
--
Brian May br...@microcomaustralia.com.au
Package: python-django
Version: 1.6.1-1
Severity: wishlist
Django's upstream has made big efforts to ensure Python3 compliance
of the code base. It would be nice if we could benefit from that work
and run Django with Python 3 on Debian systems.
Cheers,
Raphaël Hertzog.
--
To UNSUBSCRIBE,
20 matches
Mail list logo
