Re: Django 1.7 preparations

2014-09-02 Thread Brian May 
On 22 August 2014 09:49, Brian May  wrote:

> I think the following bug I just noticed is significant. Unless fixed, it
> means that after Django 1.7 is released Debian won't have a Mysql library
> for it that works with Python3.
>
> https://bugs.debian.org/758844
> http://bugs.mysql.com/bug.php?id=72542
>

Seems like it was fixed upstream, but they didn't bother to update that bug
report, so I was in the dark.

http://dev.mysql.com/doc/relnotes/connector-python/en/news-1-2-3.html
-- 
Brian May

Re: Django 1.7 preparations

2014-08-25 Thread Brian May 
On 22 August 2014 09:49, Brian May  wrote:

> I think the following bug I just noticed is significant. Unless fixed, it
> means that after Django 1.7 is released Debian won't have a Mysql library
> for it that works with Python3.
>
> https://bugs.debian.org/758844
> http://bugs.mysql.com/bug.php?id=72542
>

If that doesn't get fixed, this might be another solution:

 https://github.com/PyMySQL/PyMySQL

There are instructions for use here
https://groups.google.com/forum/#!topic/django-users/BX2o8Xkg0YY:

import pymysql
pymysql.install_as_MySQLdb()

DATABASES = {
'default': {
'ENGINE': 'django.db.backends.mysql',
. . . .

>
>
I can't help but think that the "install_as_MySQLdb()" seems a bit dodgy.
However this might be a solution if Oracle doesn't fix the
mysql-connector-plugin in time for Jessie.
-- 
Brian May

Re: Django 1.7 preparations

2014-08-21 Thread Brian May 
I think the following bug I just noticed is significant. Unless fixed, it
means that after Django 1.7 is released Debian won't have a Mysql library
for it that works with Python3.

https://bugs.debian.org/758844
http://bugs.mysql.com/bug.php?id=72542
-- 
Brian May

Re: Django 1.7 preparations

2014-08-17 Thread Thomas Goirand 
On 08/17/2014 10:58 AM, Brian May wrote:
> On 17 August 2014 12:26, Brian May  > wrote:
> 
> On second thoughts, after reading past emails on python-oauth2 in
> this group, it sounds like django-oauth-plus needs a RC bug to use
> python-oauthlib instead of python-oauth2. Will open such a bug now.
> 
> 
> Just opened the following list of bugs:
> 
> Bug #758386 [src:django-oauth-plus] depends on insecure and unmaintained
> python-oauth2
> Bug #758387 [src:djangorestframework] depends on insecure and
> unmaintained python-oauth2
> Bug #758388 [src:python-django-social-auth] depends on insecure and
> unmaintained python-oauth2
> Bug #758389 [src:turses] depends on insecure and unmaintained python-oauth2

Thanks for filing these bugs!

Thomas


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53f07916.6020...@debian.org

Re: Django 1.7 preparations

2014-08-16 Thread Brian May 
On 17 August 2014 12:26, Brian May  wrote:

> On second thoughts, after reading past emails on python-oauth2 in this
> group, it sounds like django-oauth-plus needs a RC bug to use
> python-oauthlib instead of python-oauth2. Will open such a bug now.
>

Just opened the following list of bugs:

Bug #758386 [src:django-oauth-plus] depends on insecure and unmaintained
python-oauth2
Bug #758387 [src:djangorestframework] depends on insecure and unmaintained
python-oauth2
Bug #758388 [src:python-django-social-auth] depends on insecure and
unmaintained python-oauth2
Bug #758389 [src:turses] depends on insecure and unmaintained python-oauth2
-- 
Brian May

Re: Django 1.7 preparations

2014-08-16 Thread Brian May 
On 17 August 2014 12:15, Brian May  wrote:

> Oddly enough python-djangorestframework is broken in testing already
> because django-oauth-plus is not in testing. This might be because of RC
> bugs in python-oauth2. #722656, #722657.
>
> Is anyone trying to fix python-oauth2 It looks like it has security
> issues that have not been touched in almost a year now.
>

On second thoughts, after reading past emails on python-oauth2 in this
group, it sounds like django-oauth-plus needs a RC bug to use
python-oauthlib instead of python-oauth2. Will open such a bug now.
-- 
Brian May

Re: Django 1.7 preparations

2014-08-16 Thread Brian May 
On 8 August 2014 07:48, Raphael Hertzog  wrote:

> It makes a total of 31 bugs that will need some attention:
>
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=python-dja...@packages.debian.org;tag=django17


Some of this bugs will affect other packages.

For example, #755598 (django-guardian), and #755655 (django-oauth-plus)
becoming RC will stuff up djangorestframework, because djangorestframework
build depends on these packages. So fixing djangorestframework isn't as
simple as fixing #755616.

Oddly enough python-djangorestframework is broken in testing already
because django-oauth-plus is not in testing. This might be because of RC
bugs in python-oauth2. #722656, #722657.

Is anyone trying to fix python-oauth2 It looks like it has security
issues that have not been touched in almost a year now.
-- 
Brian May

Re: Django 1.7 preparations

2014-08-09 Thread Brian May 
On 8 August 2014 07:48, Raphael Hertzog  wrote:

> I rebuilt all reverse deps of python-django and I tagged confirmed all the
> associated bugs where the package failed to build with python-django 1.7
> and I sent the relevant extract of the build log...
>

Hello,

I noticed python-kombu build depends on python-django, and the binary
packages suggest python-django.

Possibly you missed this package, as the django support is optional.

Is it ok if package supplies a "migrations" directory containing south
migrations? My preliminary tests seem to indicate that Django 1.7 can
ignore these successfully.

Thanks
-- 
Brian May

Re: Django 1.7 preparations

2014-08-08 Thread Matthias Klose 
Am 07.08.2014 um 23:48 schrieb Raphael Hertzog:
> Hi,
> 
> I rebuilt all reverse deps of python-django and I tagged confirmed all the
> associated bugs where the package failed to build with python-django 1.7
> and I sent the relevant extract of the build log...

a lot of django packages are still built with python-support. would it be
possible to switch to dh_python too when moving to 1.7?


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53e49476.5060...@debian.org

Re: Django 1.7 preparations

2014-08-07 Thread Brian May 
On 8 August 2014 07:48, Raphael Hertzog  wrote:

> It makes a total of 31 bugs that will need some attention:
>
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=python-dja...@packages.debian.org;tag=django17



django-celery - this bug is easy to work around. Waiting to see if upstream
will respond before uploading a patched version to Debian.
https://github.com/celery/django-celery/issues/336

djangorestframework - I am interested in this package, however don't
actually use it. The maintainer doesn't appear to be responsive to bug
reports, although still need to wait a bit longer before coming to a true
verdict on this. Would like to see this being maintained by the Debian
Python Modules Team.

django-filter - Somehow I completely missed the fact this bug was reopened
(#755635). Think this is a broken test only. Submitted upstream as
https://github.com/alex/django-filter/issues/157.

Hope I haven't missed other bugs :-).
-- 
Brian May