Re: dh_python3 inocrrect dependancy

thought maybe the dh_python2 man page, it isn't there. -- Brian May br...@microcomaustralia.com.au

Re: dh-python wheezy backport

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

Re: python-django-jsonfield

On 4 July 2014 12:13, Brian May br...@microcomaustralia.com.au wrote: I tried to go back to the correct version, django-jsonfield. It doesn't appear to work properly with Python3, something that I require. It imports six, but this seems to be very much incomplete. The tests fail under Python3

Re: pillow

On 2 July 2014 12:21, Brian May br...@microcomaustralia.com.au wrote: Just wondered if anybody has compiled the pillow package on wheezy? I ended up with something that appears to work, although some of the changes included: * Removing versions from dependencies on various things are too old

python-django-jsonfield

run without any problems. Can I switch to jsonfield? Or does the risk of breaking something outweigh the benefits of a Python3 package in Debian? Any other comments? Thanks -- Brian May br...@microcomaustralia.com.au

dh_python3 inocrrect dependancy

solution here? Maybe something like: echo futures python3 debian/py3dist-overrides Thought I should check here before going ahead and doing the wrong thing :-) Thanks= -- Brian May br...@microcomaustralia.com.au

dh-python wheezy backport

to backports, however I don't entirely understand this code, so not absolutely sure I got this correct. Attached is the patch for version in sid. Thanks -- Brian May br...@microcomaustralia.com.au diff -ruN dh-python-1.20140511.old/debian/changelog dh-python-1.20140511/debian/changelog --- dh

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

On 28 June 2014 17:35, Thomas Goirand z...@debian.org wrote: I just saw that Brian May added some commits in the SVN to add Python3 support to it. :) Brian, what's left to do before the upload? See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736878 Basically everything is done, except

Re: Is python-django still maintained in DPMT svn?

had similar concerns myself. -- 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: django-south will be included in Django 1.7, and as such will have Python 3 support. They have just released 1.7RC1, so it should be too much longer before 1.7 is released. Obviously I meant to say should not be too much longer. I

Re: conflict python-captcha vs django-captcha

, if I get time. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736878 -- Brian May br...@microcomaustralia.com.au

Re: conflict python-captcha vs django-captcha

Hello, Just noticed that Olivier Sallou did a new upload of python-captcha recently, so presumably this means there is some interest in keeping python-captcha in Debian. Have CCed him in case he can offer any opinions. Thanks. On 5 May 2014 09:58, Brian May br...@microcomaustralia.com.au wrote

Re: conflict python-captcha vs django-captcha

python module names are case sensitive, this thing can happen and we shouldn't preclude the two different modules being in Debian. My latest thought is maybe I should rename to: python-django-captcha and create: python3-django-captcha -- Brian May br...@microcomaustralia.com.au

Re: conflict python-captcha vs django-captcha

the best naming scheme is. So would it be acceptable to have two packages in Debian: python-captcha provides Captcha module django-simple-captcha provides captcha module Should I go ahead anyway and upload django-simple-captcha to Debian and see if anyone opens a bug report? Thanks -- Brian

Re: conflict python-captcha vs django-captcha

the best naming scheme is. This package supports Python 3. What should I call the python3 package? -- Brian May br...@microcomaustralia.com.au

Bug#750396: ITP: python-ldap3 -- A strictly RFC 4511 conforming LDAP V3 pure Python client

Package: wnpp Severity: wishlist Owner: Brian May b...@debian.org * Package name: python-ldap3 Version : 0.9.3.3 Upstream Author : Giovanni Cannata python3l...@gmail.com * URL : https://pypi.python.org/pypi/python3-ldap * License : GPLv3 Programming Lang

conflict python-captcha vs django-captcha

hard to justify when development of the conflicting package is dead. * Remove python-captcha from Debian. Nothing appears to depend on it in the Debian archive. Any thoughts? Thanks -- Brian May br...@microcomaustralia.com.au

dh_auto_* and Makefile

setup.py? I have tried providing override_dh_auto_*, but then I hard coded the python version to use. Or should I create a patch in debian/patches that removes the Makefile? This seems to be the simplest solution, but want to make sure it sounds reasonable. Thanks -- Brian May br

building python debian packages and virtualenv

this before uploading the package, however think it is only a matter of time before I stuff up an upload. Just wondering if it would be considered appropriate to have, say, dh_auto_build fail if it is about to call setup.py and it is inside a virtualenv. Just a thought. Thanks. -- Brian May br

Re: dh_auto_* and Makefile

mentioned in the dh_auto_install man page, and I wasn't sure what value to use. -- Brian May br...@microcomaustralia.com.au

Re: pbs python

Debian? It looks like it isn't supported any more... it shouldn't be a problem (pbs != bps) Oops. No wonder I couldn't find the above page :-) -- Brian May br...@microcomaustralia.com.au

Re: pbs python

is that python packages are suppose to be distributed with a setup.py, not a setup.py.in. -- Brian May br...@microcomaustralia.com.au

pbs python

this might have been renamed recently to python-sh, but can't find the reference right now) If that is not bad enough, looks like there is another python-bps too: https://gitorious.org/python-blip https://pypi.python.org/pypi/python-bps Thanks -- Brian May br...@microcomaustralia.com.au

Re: python-future: clean single-source support for Python 2/3

that contains a Future class, and having another future module that isn't remotely related. At least now we know it is something to watch out for. -- Brian May br...@microcomaustralia.com.au

python-future: clean single-source support for Python 2/3

if there is any interest. Thanks -- Brian May br...@microcomaustralia.com.au

svn error

-modules/packages/django-ajax-selects/tags/1.3.3-1' failed in '/home/brian/tree/debian/django-ajax-selects', how to continue now? [Qri?]: debian/patches/update_urls is a file that was deleted in this version. Also feel free to consider this a request to move to git :-) Thanks -- Brian May br

Re: python-django build weirdness

. The latter does some cleanup and reinitialization after each testcase, which is necessary, but isn't happening here. Fixing the import line should do the trick. Guess I should file a bug report against python-django then... -- Brian May br...@microcomaustralia.com.au

python-django build weirdness

more tests, however this is just plain weird. Will try rebooting my system in case of some weird kernel issue (currently running 3.10-0.bpo.2-amd64). Also, I didn't have any problems with python-django version 1.5.1-2 -- Brian May br...@microcomaustralia.com.au

Re: python-django build weirdness

is on tmpfs though. Not surprised... -- Brian May br...@microcomaustralia.com.au

Re: django-ajax-selects

On 1 August 2013 22:25, Jakub Wilk jw...@debian.org wrote: Really? I thought it was based on the package name. So I guess this means I got my other package, already uploaded to Debian, wrong: python-django-filter instead of python-django-filters :-(. .oO(

Re: django-ajax-selects

On 1 August 2013 15:09, Brian May br...@microcomaustralia.com.au wrote: 1. My python-ajax-select contains ./usr/share/pyshared/ajax_select/LICENSE.txt despite my debian/debian/python-ajax-select.pyremove file. W: python-ajax-select: extra-license-file usr/share/pyshared/ajax_select

Re: django-ajax-selects

-directory usr/share/pyshared/ajax_select/templates/ Can anyone see what I am doing wrong? Thanks -- Brian May br...@microcomaustralia.com.au

Re: django-ajax-selects

if the binary package ships multiple modules. In the latter case the maintainer chooses the name of the module which represents the package the most. However the word preferably suggests this is optional. -- Brian May br...@microcomaustralia.com.au

Re: django-ajax-selects

x: python-django-ajax-selects: incorrect-package-name python-ajax-select I don't know where it is getting the python-ajax-select name from. If I don't get any responses here, I will assume my package is fine. -- Brian May br...@microcomaustralia.com.au

Re: django-ajax-selects

uploaded the binary packages themselves anywhere yet. The old packages (including current orig.tar.gz) are still in Debian/unstable. -- Brian May br...@microcomaustralia.com.au

django-ajax-selects

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

Re: django-ajax-selects

-select What is the problem here? -- Brian May br...@microcomaustralia.com.au

Re: PEP 394 and shebang lines for /usr/bin/python2 scripts

On 25 July 2013 07:52, Piotr Ożarowski pi...@debian.org wrote: When my co-worker (who doesn't use Debian on his desktop/laptop machines) asked me if Debian will change the /usr/bin/python symlink anytime soon and I told him over my (or python2.X's) dead body, he responded with: that's why I

Re: Joining Python Modules Packaging Team

On 9 June 2013 08:56, Jakub Wilk jw...@debian.org wrote: python-django-tables2 python-django-filters python-ajax-select Out of curiosity, why python-ajax-select and not, python-django-ajax-select? -- Brian May br...@microcomaustralia.com.au

django-tables package

://docs.djangoproject.com/en/dev/_objects/... Seems to suggest that it is getting files from external locations during the build. If this is a problem, how do I fix it? Thanks -- Brian May br...@microcomaustralia.com.au

Re: django-tables package

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

Re: Joining Python Modules Packaging Team

as the python code). -- Brian May br...@microcomaustralia.com.au

Joining Python Modules Packaging Team

been told that those package names should be prefixed with python- to be policy compliant - just one of the things that needs fixing) Thanks -- Brian May br...@microcomaustralia.com.au

Re: karaage

what method should I use? Or should I leave that to the sysadmin to configure? Note: I personally consider it a sysadmin task to configure the database used, so it won't work out of the box. Thanks Please CC me, I am not subscribed. -- Brian May br...@microcomaustralia.com.au -- To UNSUBSCRIBE

Re: karaage

then trying to use import everywhere (as i was). It is the weekend here now, will try it for sure next Monday. -- Brian May br...@microcomaustralia.com.au -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

karaage

). Thanks. -- Brian May br...@microcomaustralia.com.au -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinfswwqq0vxpeskclnuitkrfzkuiucp_eeur...@mail.gmail.com

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

+++--- ii bzrtools 0.9.0-1 Collection of tools for bzr -- Brian May [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

bzr as root, nor have I had any reason to do so. This doesn't mean I didn't do it accidently, but I don't think so. -- Brian May [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

<    1   2   3   4