Is python-django still maintained in DPMT svn?
I ask because: % rmadison python-django | grep sid python-django | 1.6.1-1| sid | source, all % debcheckout -a --source=never python-django ... % grep -i svn debian/control Vcs-Svn: svn://anonscm.debian.org/python-modules/packages/python-django/trunk/ % head debian/changelog python-django (1.5.3-1) unstable; urgency=high % apt-get source python-django ... % head debian/changelog python-django (1.6.1-1) unstable; urgency=medium As the package is supposed to be team maintained, I'm wondering *where* it's maintained. I have some patches to fix build failures against Sphinx 1.2.1. Cheers, -Barry PS. I suppose I should add myself to Uploaders? signature.asc Description: PGP signature
Re: Is python-django still maintained in DPMT svn?
Hi Barry, On Tue, 28 Jan 2014, Barry Warsaw wrote: As the package is supposed to be team maintained, I'm wondering *where* it's maintained. I have some patches to fix build failures against Sphinx 1.2.1. Good question. Luke, are you using git-svn and you forgot to push or something? PS. I suppose I should add myself to Uploaders? Not required if you don't intend to work regularly on it. Just put Team upload in the changelog and lintian will be happy. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- 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/20140128131627.gc15...@x230-buxy.home.ouaza.com
Re: Joining the PAPT with roundup
On Jan 27, 2014, at 10:50 PM, Kai Storbeck wrote: Should I replay my git commits on subversion, or can I create a huge commit that will show the work done up to now? Would someone be interested in the small intermediate commits? They sound boring to me :) IMHO it's up to you, but Subversion being what it is, it's probably fine to just mass catchup in one big commit. -Barry signature.asc Description: PGP signature
Re: Is python-django still maintained in DPMT svn?
Hi Raphaël, On Jan 28, 2014, at 02:16 PM, Raphael Hertzog wrote: Hi Barry, As the package is supposed to be team maintained, I'm wondering *where* it's maintained. I have some patches to fix build failures against Sphinx 1.2.1. Good question. Luke, are you using git-svn and you forgot to push or something? Let me know; if not I can just update svn by slamming `apt-get source`s debian/ over the svn version. PS. I suppose I should add myself to Uploaders? Not required if you don't intend to work regularly on it. Just put Team upload in the changelog and lintian will be happy. Cool. I may also take a look at #736878 (Python 3 support). -Barry signature.asc Description: PGP signature
Re: Is python-django still maintained in DPMT svn?
I most probably did forget to push; I'll take a look later today. Thanks for the poke, Raphaël, and thanks Barry for helping with the package! I've been lagging on adopting Python3 myself; it'll be great to have Django removed from the list of blockers for that transition. :) -- Luke On 28 Jan 2014 09:03, Barry Warsaw ba...@debian.org wrote: Hi Raphaël, On Jan 28, 2014, at 02:16 PM, Raphael Hertzog wrote: Hi Barry, As the package is supposed to be team maintained, I'm wondering *where* it's maintained. I have some patches to fix build failures against Sphinx 1.2.1. Good question. Luke, are you using git-svn and you forgot to push or something? Let me know; if not I can just update svn by slamming `apt-get source`s debian/ over the svn version. PS. I suppose I should add myself to Uploaders? Not required if you don't intend to work regularly on it. Just put Team upload in the changelog and lintian will be happy. Cool. I may also take a look at #736878 (Python 3 support). -Barry
Multiple copies of timeoutsocket.py in Debian packages
Hi. A quick search on http://codesearch.debian.net reports many hits for the timeoutsocket.py library. I think it would be better to have a distinct package, then (hence a RFP: #736935). However I don't have a clue whether this is really used by these packages, if multiple versions co-exist, etc. I haven't played with sockets in Python yet. I'm tempted to think that it may even no longer be needed at all, judging from http://bugs.python.org/issue555085 if the feature was added to Python's standard library. I don't know if/what to do more on the topic... Anyone willing to try and dig on this issue ? Hth. Best regards, [0] http://codesearch.debian.net/search?q=TimeoutSocket+path%3Atimeoutsocket.py -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- 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/87ppnc5d5b@inf-8660.int-evry.fr
Re: Multiple copies of timeoutsocket.py in Debian packages
* Olivier Berger olivier.ber...@telecom-sudparis.eu, 2014-01-28, 16:39: A quick search on http://codesearch.debian.net reports many hits for the timeoutsocket.py library. I think it would be better to have a distinct package, then (hence a RFP: #736935). However I don't have a clue whether this is really used by these packages, if multiple versions co-exist, etc. I haven't played with sockets in Python yet. I'm tempted to think that it may even no longer be needed at all, judging from http://bugs.python.org/issue555085 if the feature was added to Python's standard library. Yeah, timeoutsocket.py looks like something that should have died a decade ago. In Python ≥ 2.3 you can set default timeout or a per-socket timeout without help of this library. planet-venus, python-feedvalidator and rawdog already use the proper Python interfaces, and only fall back to timeoutsocket when they are not available: http://sources.debian.net/src/python-feedvalidator/0~svn1022-2/feedvalidator/__init__.py#L8 http://sources.debian.net/src/planet-venus/0~git9de2109-1/planet/spider.py#L378 http://sources.debian.net/src/rawdog/2.13.dfsg.1-1/rawdoglib/feedparser.py#L103 plucker and spikeproxy would have to be ported to the “new” API. -- Jakub Wilk -- 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/20140128175053.ga5...@jwilk.net
Re: Is python-django still maintained in DPMT svn?
On 01/28/2014 10:03 PM, Barry Warsaw wrote: Cool. I may also take a look at #736878 (Python 3 support). This would be much much much appreciated if someone took care of that one indeed! :) And the sooner the better, so that reverse dependencies we maintain can also support Python 3. Cheers, Thomas -- 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/52e7f7a2.8090...@debian.org
Re: Multiple copies of timeoutsocket.py in Debian packages
Olivier Berger olivier.ber...@telecom-sudparis.eu writes: I'm tempted to think that it may even no longer be needed at all, It's only needed for Python 2.2 and earlier; it should be quite safe to replace with the built-in equivalents on any modern version of Python. (You may find that programs aren't using it anyway if they spot the modern version is available; e.g. feedparser and rawdog both used to use timeoutsocket as a fallback, and have removed this more recently when dropping support for older Python versions.) If you've got code that used to do: timeoutsocket.setDefaultSocketTimeout(n) # the most common usage somesocket.set_timeout(n) somesocket.get_timeout() then the modern equivalents are: socket.setdefaulttimeout(n) somesocket.settimeout(n) somesocket.gettimeout() Thanks, -- Adam Sampson a...@offog.org http://offog.org/ -- 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/y2afvo89flc@cartman.at.offog.org
