Hi,
On Tue, 16 Sep 2014, Brian May wrote:
> On 11 September 2014 16:39, Brian May
> wrote:
>
> > Ok, will look into this tomorrow.
> Just pushed a change.
>
> Unfortunately, had problems testing this because "debian/rules clean"
> removes Django.egg-info/* which is flagged by git-buildpackage a
On 11 September 2014 16:39, Brian May
wrote:
> Ok, will look into this tomorrow.
>
>
Just pushed a change.
Unfortunately, had problems testing this because "debian/rules clean"
removes Django.egg-info/* which is flagged by git-buildpackage as
uncommitted changes.
Also django-migrate-south won't
On 11 September 2014 16:28, Raphael Hertzog wrote:
> Please document this in python-django's README.Debian and mention where to
> find this sample in the current debian/python-django.NEWS entry.
>
Ok, will look into this tomorrow.
Also noticed that /usr/bin/django-admin has Python 2.6 stuff tha
Hi Brian,
thanks for those investigations!
On Thu, 11 Sep 2014, Brian May wrote:
> Note that I have explicitly called python. This ensures Python 3 not used
> (not supported by South + the virtualenv is Python 2 only) and that we get
> the python from the virtualenv.
>
> I have tested this and i
On 7 August 2014 10:19, Brian May wrote:
> virtualenv --system-site-packages ~/old_django
> . ~/old_django/bin/activate
> pip install django==1.6.5
> pip install django-south
> django-admin --settings=??? migrate --all
>
Calling django-admin like that won't use the virtualenv.
> touch /etc/xyz
On Thu, 07 Aug 2014, Brian May wrote:
> On 23 July 2014 15:58, Brian May wrote:
>
> > You are expected to do all database migrations with Django 1.6, then
> > upgrade to Django 1.7
> >
>
> Some more thoughts.
>
> Are there any packages in Debian that attempt to automatically do database
> migra
On 23 July 2014 15:58, Brian May wrote:
> You are expected to do all database migrations with Django 1.6, then
> upgrade to Django 1.7
>
Some more thoughts.
Are there any packages in Debian that attempt to automatically do database
migrations on upgrade?
If, not, that is good. Will solve the p
Hi,
Barry Warsaw:
> >- beautifulsoup
>
> Would it be better to port to dependencies to beautifulsoup4 which is already
> Python 3 compatible upstream and available in Debian as python{,3}-bs4? The
> upstream docs claim it's pretty compatible, albeit with some deprecated
> (non-PEP 8 compliant) n
On 08/04/2014 11:30 PM, Barry Warsaw wrote:
> On Aug 04, 2014, at 11:05 PM, Thomas Goirand wrote:
>
>> Well, I'm doing my best to add Python 3 support everywhere I can.
>
> \o/
>
>> I've been doing this for months already. I know it wont be possible to fix
>> everything. Currently, I have 2 bloc
Hi,
On Mon, 04 Aug 2014, Thomas Goirand wrote:
> and already found out that TEMPLATE_DIRS needed an additional comma in
> settings.py, though there's still a lot more failure in the unit tests.
> If you want to help, just try to rebuild Horizon (and add a comma as I
> wrote in horizon/tests/settin
On 4 August 2014 10:29, Thomas Goirand wrote:
> Also, fixing version 3 of beautifulsoup doesn't look very easy. It needs
> sgmllib, which is removed from Python 3, and it doesn't feel right to
> maintain sgmllib as a Python module for Python 3 (I tried, and with a
> few hacks, it works though...)
On 08/04/2014 11:30 PM, Barry Warsaw wrote:
> On Aug 04, 2014, at 11:05 PM, Thomas Goirand wrote:
>
>> Well, I'm doing my best to add Python 3 support everywhere I can.
>
> \o/
>
>> I've been doing this for months already. I know it wont be possible to fix
>> everything. Currently, I have 2 bloc
On Aug 04, 2014, at 11:05 PM, Thomas Goirand wrote:
>Well, I'm doing my best to add Python 3 support everywhere I can.
\o/
>I've been doing this for months already. I know it wont be possible to fix
>everything. Currently, I have 2 blockers which I am working on:
>
>- python-memcache
>- beautifu
On 08/03/2014 03:27 PM, Raphael Hertzog wrote:
> On Sun, 03 Aug 2014, Brian May wrote:
>>> Django 1.7 final isn't even released upstream, and therefore, downstream
>>> projects didn't even try to run against it. There *will* be issues we
>>> will have to deal with. 85 packages is quite something. I
On 3 August 2014 15:07, Brian May wrote:
> It will be released very soon now. They have released RC2, and I heard, as
> of yesterday, there was only one blocking bug (I am at PyConAu).
>
It sounds like there might be be some effort to make Django 1.7 releasable
at the post-conference sprints, st
On Sun, 03 Aug 2014, Brian May wrote:
> > Django 1.7 final isn't even released upstream, and therefore, downstream
> > projects didn't even try to run against it. There *will* be issues we
> > will have to deal with. 85 packages is quite something. I'm ok, and even
> > welcome to *try* to make it b
On 3 Aug 2014 14:53, "Brian May" wrote:
>> Django 1.7 final isn't even released upstream, and therefore, downstream
>> projects didn't even try to run against it. There *will* be issues we
>> will have to deal with. 85 packages is quite something. I'm ok, and even
>> welcome to *try* to make it be
Raphael said he is not subscribed, so I have sent this to him.
On 3 Aug 2014 14:13, "Thomas Goirand" wrote:
> On 07/23/2014 08:27 AM, Brian May wrote:
> > Hello,
> >
> > Thanks for you work. I very much agree, would really like to see Django
> > 1.7 in Jessie, even if it does break some things al
On 07/23/2014 08:27 AM, Brian May wrote:
> Hello,
>
> Thanks for you work. I very much agree, would really like to see Django
> 1.7 in Jessie, even if it does break some things along the way.
I don't agree with the last bit of your sentence.
Django 1.7 final isn't even released upstream, and the
On 23 July 2014 16:46, Raphael Hertzog wrote:
> - the settings needs to include South only in Django < 1.7, you can do
> this for example:
>
> import django
> if django.VERSION < (1, 7):
> INSTALLED_APPS += ('south',)
>
Even better (hope I get this right):
=== cut ===
import sys
imp
On 23 Jul 2014 16:46, "Raphael Hertzog" wrote:
> - we should package South 1.0, it uses "south_migrations" instead of
> "migrations" if it exists, that way applications can provide migrations
> for South and for Django 1.7
Already done. Uploaded and installed in Debian unstable today.
Was st
Hi,
On Wed, 23 Jul 2014, Brian May wrote:
> Attempt to summarize the problem: You want to make sure Django 1.7 is never
> installed if there are any apps with Django south migrations that haven't
> been run, and if Django 1.7 is installed you want to make sure django-south
> is not in INSTALLED_AP
On 23 July 2014 12:54, Brian May wrote:
> I think django-south still works with Django 1.7 (), but is considered
> depreciated compared with the Django 1.7 built in migrations.
>
I was wrong. django-south will not work with 1.7, and quite possibly never
will work with Django 1.7 - I haven't
Just testing some of my code against Django 1.7.
The first problem was this:
Unhandled exception in thread started by
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/django/utils/autoreload.py", line
221, in wrapper
fn(*args, **kwargs)
File
"/usr/lib/python2.7/d
On 23 July 2014 10:27, Brian May wrote:
> Something seems to have gone wrong with your package.
>
Looks like you already fixed it in -2.
I have back ported this to wheezy.
In case anybody wants to use it, and actually trusts me (why would anybody
trust me?), you can use at by adding the follow
Hello,
Thanks for you work. I very much agree, would really like to see Django 1.7
in Jessie, even if it does break some things along the way.
Something seems to have gone wrong with your package.
Both python-django and python3-django include
/usr/bin/django-admin
...and as a result conflict.
(Please cc me as I'm not subscribed)
Hello,
I have filed 85 bugs against all reverse-deps of python-django
to ask their maintainers to ensure that their packages works well
with Django 1.7 (1). A good chunk of those are maintained or co-maintained
by the Python Modules team, and as usual in a lar
27 matches
Mail list logo
