tagging releases in git

According to the wiki I do this with the following command: brian@prune:~/tree/debian/python-modules/django-ajax-selects$ git-dpm tag git-dpm: ERROR: tag 'upstream/1.3.6' already exists and differs! This wasn't the response I was expecting. I am not sure why it is trying to change the upstream

Re: git.debian.org broken link

On Sat, 10 Oct 2015 at 16:43 Scott Kitterman wrote: > http://git.debian.org/?p=python-modules/packages/ redirects to > http://anonscm.debian.org/cgit/python-modules/packages which doesn't show > a > repository for django-ajax-selects, so it looks like it's actually missing.

git.debian.org broken link

When I fixed a bug in git: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801208 It put a link to a diff in the bug report: http://git.debian.org/?p=python-modules/packages/django-ajax-selects.git;a=commitdiff;h=9d026b4 Initially this was coming up with "Internal Server Error". Now it is

Re: Python < 3.5 tests

On Thu, 8 Oct 2015 at 22:44 Dmitry Shachnev wrote: > Python 3.4 is still the default version in Debian. We can't do the switch > at once, so the transition is split into three steps: > > 1) Add Python 3.5; > 2) Make 3.5 the default; > 3) Remove Python 3.4. > > We are

Re: Python < 3.5 tests

On Thu, 8 Oct 2015 at 22:44 Dmitry Shachnev wrote: > > There was a change in unittest autoloader in Python 3.5. It now tries to > import the package even if it has no tests. I do not know if it is an > intended change, or a side-effect of fixing some bug ([1]?). Maybe Robert

Re: Python < 3.5 tests

On Fri, 9 Oct 2015 at 08:16 Robert Collins wrote: > But - ajax_select/__init__.py is going to be imported, and thats whats > erroring. I don't think that this is a 3.5 unit testing change - I > think its an error importing some bit of django. > On 2nd thoughts, I

Re: Python < 3.5 tests

On Fri, 9 Oct 2015 at 08:49 Robert Collins wrote: > The reason it's being discovered is likely due to the pattern bugfix > (also in 3.5) - previously discover couldn't handle directories with > names tht didn't match the file pattern - and that meant nested test >

Re: Git migration schedule

On Fri, 9 Oct 2015 at 02:06 Stefano Rivera wrote: > Done. And kicking off the migration now... > Great! Will the migration do packages like python-django? Just thinking that python-django in subversion is old, and the version in git doesn't (yet) use git-dpm; you don't

Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental

On Thu, 8 Oct 2015 at 00:32 Thomas Goirand wrote: > You've only enforced *your own* policy, backed-up by only a small vocal > minority, taking the rule to the extreme (ie: a few days before the Git > migration, it's still not ok to start new projects using Git, according > to

Python < 3.5 tests

Hello, When debugging #801208, I noticed the following output: dh_auto_test -O--buildsystem=pybuild I: pybuild base:170: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover -v -- Ran 0

Re: managing transitions (was: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental)

On Tue, 6 Oct 2015 at 18:46 Thomas Goirand wrote: > This IMO is the same topic as having a Gerrit review system (and not > just Git) which could do tests on each change of a package even before > having them committed to our git. > Sounds like an interesting thing to

Re: Git migration schedule

On Tue, 6 Oct 2015 at 02:49 Barry Warsaw wrote: > Waiting longer isn't an option IMHO. It's helping to add to the > dysfunction > of the team. I will also offer to help if the 3.5 transition gets stuck > because of the git conversion. > Hurry up and break my packages :-) Do

Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental

On Tue, 6 Oct 2015 at 09:33 Scott Kitterman wrote: > Except in this case you not only didn't but then got defensive when called > on it. If you'd just reacted with something like "Oops, made a mistake, > I'll > revert it from svn and ask for it to be removed from

Re: [DPMT] radical changes: automation, carrot and stick

On Mon, 5 Oct 2015 at 08:54 Stefano Rivera wrote: > There's a fundamental question to ask here. Do we want to welcome Python > packages into the team, or do we want to put up barriers and require a > level of commitment before packages can be brought into the team?

Bug#794829: ITP: python-django-cors-headers -- Django app for handling the server headers required for Cross-Origin Resource Sharing (CORS)

Package: wnpp Severity: wishlist Owner: Brian May b...@debian.org * Package name: python-django-cors-headers Version : 1.1.0 Upstream Author : Otto Yiu * URL : https://github.com/ottoyiu/django-cors-headers/ * License : MIT Programming Lang: Python2

Re: Bug#785275: ITP: python-ipaddress -- Backport of the ipaddress module from Python 3.3

On Fri, 22 May 2015 at 07:14 Scott Kitterman deb...@kitterman.com wrote: I was considering the idea of porting things from ipaddr to ipaddress for python2, but there's a lot more of that then there is for ipaddress (which is up to only two packages we know about). As it is a goal to have

Re: python3-xlib lost in Debian

On Mon, 27 Apr 2015 at 12:26 mudongliang mudonglianga...@hotmail.com wrote: Today I try to install a software - youdao dict. First I try it in vmware machine: Linuxmint and Ubuntu. It can succeed! But when I do it in Debian , it fails ; And the reason is the lost of python3-xlib. So I search

Re: [Python-modules-team] Bug#782756: should not be in Section: python

On Tue, 21 Apr 2015 at 14:38 Damyan Ivanov d...@debian.org wrote: Its description says static site generator. Sounds a lot like HTTP to me, not less than ikiwiki for example. I think you might be getting HTTP confused with HTML. Both ikiwiki and mkdocs turn files into static HTML files, but

Re: [Python-modules-team] Bug#782756: should not be in Section: python

On Mon, 20 Apr 2015 at 10:44 Ben Finney ben+deb...@benfinney.id.au wrote: What does the package primarily install? Would you characterise the work's purpose as: * web: “Web servers, browsers, proxies, download tools etc.” Doesn't seem applicable, it doesn't do anything with HTTP. * utils:

Re: Build separate binary packages from single source

-server http://pypi.python.org/pypi/devpi-web http://pypi.python.org/pypi/devpi-client As each one has its own version number, and presumably its own release cycle, presumably you should be packaging them as separate Debian source packages. -- Brian May br...@microcomaustralia.com.au

Re: Bug#778269: ITP: python-mkdocs -- Static site generator geared towards building project documentation

On 14 February 2015 at 09:52, Brian May b...@debian.org wrote: What should I call the package? mkdocs? Or python3-mkdocs? Thinking about this, I will call the source python-mkdocs, but the binary package just mkdocs. As I think the names python-mkdocs and python3-mkdocs imply some sort

Re: Bug#778269: ITP: python-mkdocs -- Static site generator geared towards building project documentation

2.5 is for Python 2.6 support, which we don't care about. -- Brian May b...@debian.org

Bug#778269: ITP: python-mkdocs -- Static site generator geared towards building project documentation

Package: wnpp Severity: wishlist Owner: Brian May b...@debian.org * Package name: python-mkdocs Version : 0.11.1 Upstream Author : Tom Christie * URL : http://www.mkdocs.org/ * License : BSD Programming Lang: Python Description : Static site generator

dh_python2 missing

in came good. Not entirely sure this is a bug that needs to be reported, however letting other people know just in case this isn't something unique to be setup on this particular computer. Thanks -- Brian May br...@microcomaustralia.com.au

Re: multiple modules in one source

On 12 December 2014 at 09:48, Ben Finney ben+deb...@benfinney.id.au wrote: Just about any non-trivial Python package (and some trivial ones) in Debian will have many distinct modules. Possibly I am getting my terminology confused. You're familiar with ‘python-django’, as just one example.

Re: multiple modules in one source

now. -- Brian May br...@microcomaustralia.com.au

multiple modules in one source

everything combined, or maybe trying to convincing upstream that they shouldn't combine the (very much related) modules into one source. (at the present it is still very much alpha and no released version yet) Thanks -- Brian May br...@microcomaustralia.com.au

Bug#770779: unblock: python-django-guardian/1.2.4-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock python-django-guardian was RC bug #763222. I believe this is a just a technical bug in the tests, the actual package should work fine. However, it means the package won't build. This in

Re: How to solve #751375, file clash

the file supplied by python-configparser? If it is the same file, you could delete it from python-pies2overrides and depend on python-configparser. -- Brian May br...@microcomaustralia.com.au

Re: Help needed to test packages with Django 1.7

On 11 September 2014 16:39, Brian May br...@microcomaustralia.com.au 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

Re: django 1.7 bugs

with Django 1.7 (e.g. if a Python Team module depends on a non-python team module). I see you remembered to CC Raphael Hertzog - thanks for that; I totally forgot. -- Brian May br...@microcomaustralia.com.au

Re: Help needed to test packages with Django 1.7

On 7 August 2014 10:19, Brian May br...@microcomaustralia.com.au 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

Re: Help needed to test packages with Django 1.7

Python 2.6 stuff that is no longer relevant, as Python2.6 isn't supported any more. Will remove this too. -- Brian May br...@microcomaustralia.com.au

django 1.7 bugs

it works with Django 1.7 Bugs forwarded upstream (may not get fixed in time for the freeze): #755585 [i| |↝] [src:dico] dico: Please ensure it works with Django 1.7 #755667 [i| |↝] [src:django-openid-auth] django-openid-auth: Please ensure it works with Django 1.7 -- Brian May br

Fwd: Processed: not a django1.7 bug

-- Forwarded message -- From: Debian Bug Tracking System ow...@bugs.debian.org Date: 9 September 2014 16:06 Subject: Processed: not a django1.7 bug To: Brian May br...@microcomaustralia.com.au Processing commands for cont...@bugs.debian.org: user python-dja...@packages.debian.org

Re: django 1.7 change for backport to wheezy

, easy to redo it. -- Brian May br...@microcomaustralia.com.au

django / python-mysql.connector / python2 / unicode broken

for Django1.6, I only have tested 1.7 myself. -- Brian May br...@microcomaustralia.com.au

django 1.7 change for backport to wheezy

% confident of the branches - I guess I should use the debian/experimental branch? Thanks -- Brian May br...@microcomaustralia.com.au

django 1.7 migrations

Python 3. Presumably if you use unicode strings everywhere or add the following to the top of model files, this wouldn't be an issue. Not tested it myself. from __future__ import unicode_literals I reported this upstream: https://code.djangoproject.com/ticket/23455 Thanks -- Brian May br

Re: python-openssl unavailable in sid

didn't respond, maybe it come good by itself? -- Brian May br...@microcomaustralia.com.au

Re: Django 1.7 preparations

On 22 August 2014 09:49, Brian May br...@microcomaustralia.com.au 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

Re: Update to Veusz 1.21.1

modules, of course), although I don't know enough about veusz to say whether this is the case or not. Also, if is an application (as opposed to module/library), there is probably no point packaging both Python3 and Python2 versions. Pick one, and package that. -- Brian May br

Re: Proposed git migration plan

, these are the ones that have annoyed me recently. Unlike some, I am happy to continue using subversion. However I feel I could do a better, more professional job with git. -- Brian May br...@microcomaustralia.com.au

Re: Django 1.7 preparations

On 22 August 2014 09:49, Brian May br...@microcomaustralia.com.au 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

Re: guardian and django1.7

On 25 August 2014 15:50, Brian May br...@microcomaustralia.com.au wrote: At the moment, am wondering if maybe this is a Django 1.7 bug. Unless I hear otherwise, I am going to assume this is a Django 1.7 bug: https://code.djangoproject.com/ticket/23360 -- Brian May br

Re: guardian and django1.7

of the problems. e.g. https://github.com/brianmay/django-guardian/blob/master/debian/patches/0008-Fix-conflicting-related_name.patch -- Brian May br...@microcomaustralia.com.au

Re: guardian and django1.7

As an experiment, I imported django-guardian from the *.dsc files to git using git-dpm, and applied my changes. Not sure if I have got this right, it was the first time I used git-dpm. The result is currently at: https://github.com/brianmay/django-guardian/tree/patched (patched branch). This is

Re: guardian and django1.7

On 19 August 2014 18:37, Brian May br...@microcomaustralia.com.au wrote: At which point I ran out of time :-) Ok, did all that. guardian does some creative things, am surprised it works under any version of Django. e.g. defining conflicting DB models, and only use one of them. Next error

Re: Django 1.7 preparations

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 br...@microcomaustralia.com.au

Re: guardian and django1.7

On 19 Aug 2014 18:37, Brian May br...@microcomaustralia.com.au wrote: On 19 Aug 2014 18:04, Raphael Hertzog hert...@debian.org wrote: Did you fill that new directory with an initial migration generated with ./manage.py makemigrations? Yes, did that, but than I realized I needed to do

python-openssl unavailable in sid

chroot? It appears that the packages produced have changed to architecture dependant packages, seriously wondering if maybe this got DAK confused. (this problem is preventing me from uploading a fix for an RC bug) Thanks -- Brian May br...@microcomaustralia.com.au

Re: python-openssl unavailable in sid

On 21 August 2014 10:42, Cyril Brulebois k...@debian.org wrote: Brian May br...@microcomaustralia.com.au (2014-08-21): Can somebody please tell me why python-openssl and python3-openssl isn't available in sid? […] It appears that the packages produced have changed to architecture

Re: guardian and django1.7

On 19 Aug 2014 18:04, Raphael Hertzog hert...@debian.org wrote: Did you fill that new directory with an initial migration generated with ./manage.py makemigrations? Yes, did that, but than I realized I needed to do testapp. So I did just testapp by itself, but suspect both django apps need to

celery / python3.2 wheezy backport

, import_path) File /usr/lib/python3/dist-packages/mock.py, line 1101, in _dot_lookup return getattr(thing, comp) AttributeError: 'module' object has no attribute 'sets' -- -- Brian May br...@microcomaustralia.com.au

librabbitmq and git

thing for 0.5.1? Thanks -- Brian May br...@microcomaustralia.com.au

Re: librabbitmq and git

/.+\/v?(\d\S*)\.tar\.gz/librabbitmq-c-$1.tar.gz/ \ https://github.com/alanxz/rabbitmq-c/releases \ /alanxz/rabbitmq-c/archive/v([\d\.]+)\.tar\.gz -- Brian May br...@microcomaustralia.com.au

Re: librabbitmq and git

changes. Not sure how. Might be better off spending my time on django-guardian instead. -- Brian May br...@microcomaustralia.com.au

Re: guardian and django1.7

On 19 August 2014 11:03, Brian May br...@microcomaustralia.com.au wrote: Any ideas how to fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755598 ? I have had a fiddle, but not really making any progress (apart from Python3 package which works fine). For example, I renamed migrations

Re: Django 1.7 preparations

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 br...@microcomaustralia.com.au

Re: Django 1.7 preparations

On 17 August 2014 12:15, Brian May br...@microcomaustralia.com.au 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

Re: Django 1.7 preparations

On 17 August 2014 12:26, Brian May br...@microcomaustralia.com.au 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

Bug#757980: ITP: cryptography -- cryptography is a package which provides cryptographic recipes and primitives to Python developers.

Package: wnpp Severity: wishlist Owner: Brian May b...@debian.org * Package name: cryptography Version : 0.5.3 Upstream Author : Various * URL : https://cryptography.io/en/latest/ * License : Apache License Programming Lang: Python Description

pyopenssl

' failed dpkg-buildpackage: error: debian/rules build gave error exit status 2 Thanks -- Brian May br...@microcomaustralia.com.au

Re: kombu vs dh_python3

On 11 August 2014 20:59, Michael Fladischer mich...@fladi.at wrote: On 2014-08-11 07:16, Brian May wrote: I have updated kombu in subversion to provide Python 3 packages. There is already a python3 branch in svn ... waiting for the python-nose test failure to be fixed. Whoops. I guess I

Re: kombu vs dh_python3

branch? If so, sounds like a good plan. Would be interested to know what is doing on with dh_python3 though... Even if the workaround is simple. -- Brian May br...@microcomaustralia.com.au

Re: kombu vs dh_python3

. -- Brian May br...@microcomaustralia.com.au

Re: kombu vs dh_python3

On 11 August 2014 21:25, Piotr Ożarowski pi...@debian.org wrote: [Brian May, 2014-08-11] Only the install phase is leaving behind empty directories under debian/python3-kombu/usr/lib/python3.4/dist-packages/kombu/ which version of dh_python3 did you use? Can you paste -v/--verbose's

Re: kombu vs dh_python3

On 11 August 2014 21:33, Brian May br...@microcomaustralia.com.au wrote: which version of dh_python3 did you use? Can you paste -v/--verbose's output? This is an up-to-date sid schroot (at least it was up-to-date yesterday). Not sure if this output helps, except for it saying moving files

Re: python3-module packages must not depend on pythonmodule packages and vice versa

. -- Brian May br...@microcomaustralia.com.au

kombu vs dh_python3

. If I remove one of the duplicate calls, I get the broken behaviour again. Thanks -- Brian May br...@microcomaustralia.com.au

Re: Two django packages for Debian?

. At the moment, in subversion, we only store the debian/* directory. Is there any requirement/benefit in putting the full upstream source in git too? -- Brian May br...@microcomaustralia.com.au

Re: Django 1.7 preparations

these successfully. Thanks -- Brian May br...@microcomaustralia.com.au

Re: Django 1.7 preparations

-filter/issues/157. Hope I haven't missed other bugs :-). -- Brian May br...@microcomaustralia.com.au

Re: Help needed to test packages with Django 1.7

On 23 July 2014 15:58, Brian May br...@microcomaustralia.com.au 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

Re: Two django packages for Debian?

in experimental... -- Brian May br...@microcomaustralia.com.au

Re: Help needed to test packages with Django 1.7

On 3 August 2014 15:07, Brian May br...@microcomaustralia.com.au 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

Re: Help needed to test packages with Django 1.7

Raphael said he is not subscribed, so I have sent this to him. On 3 Aug 2014 14:13, Thomas Goirand z...@debian.org 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

Re: Help needed to test packages with Django 1.7

On 3 Aug 2014 14:53, Brian May br...@microcomaustralia.com.au 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

Re: python3 celery

On 14 Jul 2014 22:21, Matthias Klose d...@debian.org wrote: Twisted has some support for Python3, see twisted/python/dist3.py in the twisted 14.0 sources. I packaged a twisted-py3 building a python3-twisted-experimental, which I didn't yet upload to Debian. For now you can get it from

Re: Problem migrating from South to Django migrations for Linux distributions

already; it wasn't in wheezy. -- Brian May br...@microcomaustralia.com.au

Re: Problem migrating from South to Django migrations for Linux distributions

installed Django apps that are not part of Debian [need some sort of evidence to back up this claim]. (as an aside, I have users of my Django app who are still running a really old version on Debian squeeze :-( ). -- Brian May br...@microcomaustralia.com.au

Re: Problem migrating from South to Django migrations for Linux distributions

it to work, I don't think I would trust it. -- Brian May br...@microcomaustralia.com.au

Re: Help needed to test packages with Django 1.7

=== import sys import django if sys.version_info (3, 0) and django.VERSION (1, 7): INSTALLED_APPS += ('south',) === cut === As south is not available for Python 3. -- Brian May br...@microcomaustralia.com.au

Re: Help needed to test packages with Django 1.7

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.

Re: Help needed to test packages with Django 1.7

On 23 July 2014 10:27, Brian May br...@microcomaustralia.com.au 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

Re: Help needed to test packages with Django 1.7

SOUTH_MIGRATION_MODULES. Which is unfortunate, it means the decision has to be made in the library, but the SOUTH_MIGRATION_MODULES has to be set in the application. -- Brian May br...@microcomaustralia.com.au

[nore...@release.debian.org: [Python-modules-team] kombu is marked for autoremoval from testing]

As far as I can tell, all of these marked for autoremovals occured because kombu had a build dependancy on python-librabbitmq, which I have changed to python-amqp, and uploaded to Debian. -- Brian May b...@debian.org ---BeginMessage--- kombu 3.0.19-1 is marked for autoremoval from testing on 2014

Re: /usr/bin/django-admin in python-django

installed. As well as maintain compatibility with existing packages. So the first approach seems to appropriate one here. -- Brian May br...@microcomaustralia.com.au

python celery broken

not be release critical. grave: makes the package in question unusable or mostly so, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package -- Brian May br...@microcomaustralia.com.au

Re: /usr/bin/django-admin in python-django

On 7 July 2014 11:55, Brian May br...@microcomaustralia.com.au wrote: The problem is that the django-admin wrapper chose the python3 version, but karaage.tests.settings is only available in Python2, even though I have python3-django installed. See bugs #755341 and #755321. Looks like code

Re: /usr/bin/django-admin in python-django

On 20 July 2014 11:12, Brian May br...@microcomaustralia.com.au wrote: See bugs #755341 and #755321. Looks like code is trying to run django-admin as a python script, allows it to specify which version of python to use. Only thing is, it isn't Python. It is now shell. This allows automatic

Re: apache2.2 / apache2.4 config

. If the user upgrades to Apache2.4, they will have to manually fix up the configuration. Which may be as simple as a2enconf someconf-2.4 (assuming the new Apache config installs without conflicts). Plus, optionally, delete the /etc/apache2/conf.d -- Brian May br...@microcomaustralia.com.au

apache2.2 / apache2.4 config

of time before I get totally confused and edit the wrong one) Anyone got any better ideas? Thanks -- Brian May br...@microcomaustralia.com.au

python3 celery

but it is not installable etc. (python3-botocore exists - can this be used instead of python3-boto?) It would be good if we could get this done by the next freeze, however, looks like a lot of packages, and I am not familiar with any of them. Thanks -- Brian May br...@microcomaustralia.com.au

Re: python3 celery

attached patch file. -- Brian May br...@microcomaustralia.com.au Index: debian/control === --- debian/control (revision 29742) +++ debian/control (working copy) @@ -2,30 +2,24 @@ Section: python Priority: optional Maintainer

Re: python3-django and mysqldb

On 7 Jul 2014 13:42, Brian May br...@microcomaustralia.com.au wrote: Which is already in unstable: python-mysql.connector python3-mysql.connector Might have to try and get these updated in Debian. http://bugs.mysql.com/bug.php?id=71806 Means Django depreciated warnings become fatal errors

Re: python3-django and mysqldb

On 7 Jul 2014 13:42, Brian May br...@microcomaustralia.com.au wrote: Which is already in unstable: python-mysql.connector python3-mysql.connector Also see https://groups.google.com/forum/m/#!topic/south-users/hrxwgimaYy8 By default south doesn't work with mysql connector. Fortunately

/usr/bin/django-admin in python-django

solution for this though. Hopefully nobody else does this :-) -- Brian May br...@microcomaustralia.com.au

python3-django and mysqldb

headers to suggest these instead of mysqldb, as mysqldb development appears to be dead. As far as I can tell this should be supported in Django 1.6 (assuming I am reading a particular line in the documentation correctly). -- Brian May br...@microcomaustralia.com.au

Re: python 3 and django (was: Is python-django still maintained in DPMT svn?)

On 28 June 2014 20:43, Brian May b...@debian.org wrote: I personally will need python3-mysqldb, python3-psycopg, and python3-flup (or equivalent). python3-psycopg: was replaced with python3-psycopg2, packages are available in wheezy and sid already. Have updated svn not to refer

<    1   2   3   4   >