Re: dh_python3 inocrrect dependancy
On 5 July 2014 02:44, Brian May br...@microcomaustralia.com.au wrote: I assumed it wasn't valid to have a line with only one value in that file. Then again, not sure where this file is documented. Would have thought maybe the dh_python2 man page, it isn't there. From the dh_python2 man page: dependencies dh_python2 tries to translate Python dependencies from requires.txt file to Debian dependencies. Use debian/pydist-overrides or --no-guessing-deps option to override it if the guess is incorrect. If you want dh_python2 to generate more strict dependencies (f.e. to avoid ABI problems) create debian/python-foo.pydist file. See /usr/share/doc/python-doc/README.PyDist (provided by python-doc package) for more information. If the pydist file contains PEP386 flag or set of (uscan like) rules, dh_python2 will make the depedency versioned (version requirements are ignored by default). From the dh_python3 man page: dependencies dh_python3 tries to translate Python dependencies from requires.txt file to Debian dependencies. Use debian/py3dist-overrides or --no-guessing-deps option to override it if the guess is incorrect. If you want dh_python3 to generate more strict dependencies (f.e. to avoid ABI problems) create debian/python3-foo.pydist file. See /usr/share/doc/dh-python/README.PyDist for more information. If the pydist file contains PEP386 flag or set of (uscan like) rules, dh_python3 will make the depedency versioned (version requirements are ignored by default). Both copies of README.PyDist (in python-doc and dh-python) seem to exist and be almost identical (main difference is that the dh-python version has a few extra words about Python 3 / dh_python3 related things which the python-doc version doesn't have). -- mithrandi, i Ainil en-Balandor, a faer Ambar -- 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/camckhmqnkm3n+b5hn5v9k2ttx5ifmrmh4nd5o+1ab_0pjis...@mail.gmail.com
Re: Bug#753590: ITP: python-pyqtgraph -- Scientific Graphics and GUI Library for Python
Hi Gianfranco, On Sat, Jul 05, 2014 at 10:41:09AM +0100, Gianfranco Costamagna wrote: Hi Andreas, thanks for doing this! I propose also to change the maintainer if you think is better, don't know ;) IMHO the maintainer should be a team (either Debian Science or Debian Python) and it seems reasonable to put the team in charge which is owning the VCS where the package is maintained. Since the package technically fits into Python and from content into Science there is no clear rule to decide. The Blends framework can be used in any case. It is no requirement to maintain a package in a certain team. Anyway I'm looking for a sponsor (I already have a busy one in debian-science), Since I think that the package clearly fits into Deban Science Blend I'm fine if you would use Sponsering of Blends: https://wiki.debian.org/DebianPureBlends/SoB One drawback of using Debian Python VCS is that it is not (yet) scanned for new packages and thus the package does not yet show up on the Science viewing page. Since I'm aware about this I would not mind about this requirement of SoB. and BTW the KGB bots in debian-science are broken (mdtx tried many times to unsuccessfully contact you, so I'm taking the opportunity to make you aware of the problem) I was contacted at least twice by somebody (may be mdtx - whoever this might be) and I answered in publich to the Debian Med maintainer list (I was contacted about Debian Med KGB) that I have no idea what needs to be done and I also have currently no time to make up my mind. I personally do not use KGB features and I expect somebody else in the team to do the necessary means to fix this. If this is considered unsuccessfully contact than yes, this was unsuccessful. But I have no idea why it should be me who should fix each and any piece of infrastructure. B-) So please in cases like this contact the team or use the BTS to report the problem. Kind regards Andreas. -- http://fam-tille.de -- 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/20140705152625.ga14...@an3as.eu
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 to the psycopg any more, it already had psycopg2. python-mysqldb: upstream does not support Python3, and development looks very deadish. http://mysql-python.sourceforge.net/ python-flup: upstream website is dead, connection times out: http://www.saddi.com/software/flup/ Pypi indicates no releases in years, and no mention of Python 3 support: https://pypi.python.org/pypi/flup I see references to a slightly newer version on the upstream website, which of course is dead: https://github.com/pld-linux/python3-flup/blob/master/python3-flup.spec links to http://hg.saddi.com/flup-py3.0/archive/cc23b715b120.tar.bz2/flup-1.0.3_20120326.tar.bz2 Possibly (hopefully!) these packages are not required any more or have been replaced by something else in Python 3, I don't know. -- Brian May b...@debian.org
