Re: python-openssl unavailable in sid

On Mon, Sep 8, 2014 at 09:57:36 +1000, Brian May wrote: > As far as I can tell, this problem has been fixed. ftp-master didn't > respond, maybe it come good by itself? No, they fixed it last week. Cheers, Julien -- Julien Cristau Logilab http://www.logilab.fr/ Informa

django 1.7 change for backport to wheezy

Hello, Can I please get the following change in python-django git? Add the following to debian/control: X-Python-Version: >= 2.7 This will make backports to stable a lot easier. Otherwise the package builds fine, but won't install in Python 2.6 is installed. I would do it myself, but not 100%

Terminal Pager at unit tests

Hi, Currently I am working on the debianization of oct2py[1] which is a bridge between Python an GNU Octave. When the tests are running the docstrings are displayed in a terminal pager making impossible run all tests without human interaction to close the pager. I've found this really annoying

django 1.7 migrations

Hello, Just noticed, if you generate Django 1.7 migrations using Python 2, they won't be Python 3 compatible. i.e. strings such as 'name' will become b'name' in the migration, which doesn't work in python 3. The work around seems to be to remove the b'...' by hand or make the migrations using Py

Fwd: Processed: not a django1.7 bug

Hello, I just tidied up this bug. It started off as a Django1.7 bug, then it got retitled to a Python3 bug. Then I wondered if maybe I should have cloned it, and retitled the original back to the original value, and closed it. If you want to refine my efforts, feel free to do so. Thanks --

Re: django 1.7 change for backport to wheezy

Hi, On Tue, 09 Sep 2014, Brian May wrote: > Can I please get the following change in python-django git? > > Add the following to debian/control: > > X-Python-Version: >= 2.7 > > This will make backports to stable a lot easier. Otherwise the package > builds fine, but won't install in Python 2.6

Re: django 1.7 change for backport to wheezy

On 9 September 2014 16:31, Raphael Hertzog wrote: > Yes, please commit that on the debian/experimental branch. > Will do that tomorrow. > (Sorry that I lost this in the git conversion.) > Thought I had made the change before. Not loosing my mind after all :-) Not a problem, easy to redo it.

Re: No __init__.py for namespaced module in Python 3.4

Hi barry, Thanks for your answer. On 09/06/2014 05:38 AM, Barry Warsaw wrote: > On Sep 05, 2014, at 11:16 PM, Thomas Goirand wrote: > >> Surprisingly, when I just do (as root): >> >> echo "" >/usr/lib/python3/dist-packages/oslo/__init__.py >> >> then everything works again, and subunit under Pyt