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
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
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
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
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
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,
* 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
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,
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
9 matches
Mail list logo
