Le 19/01/2011 18:04, Georg Brandl a écrit :
Am 19.01.2011 16:25, schrieb Eric Smith:
Bonus question: if we remove maintainers.rst from py3k, what do we do in
3.1 and 2.7? I’d favor removing them over keeping outdated versions.
Is there not some advantage to knowing who was the maintainer (or
On Wed, Feb 2, 2011 at 11:48, Éric Araujo mer...@netwok.org wrote:
Le 19/01/2011 18:04, Georg Brandl a écrit :
Am 19.01.2011 16:25, schrieb Eric Smith:
Bonus question: if we remove maintainers.rst from py3k, what do we do in
3.1 and 2.7? I’d favor removing them over keeping outdated versions.
Short of moving README.coverity (I'm waiting to here back from the
company), I'm done with my tweaks to the directory.
On Wed, Jan 19, 2011 at 15:31, Brett Cannon br...@python.org wrote:
OK, here is my plan that I will implement:
MOVE
--
developers.txt
maintainers.rst
README.gdb
Brett,
I'm sure I just missed it, but where is the devguide in the Subversion tree?
Thx,
Skip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
It's not in the svn tree; it's an Hg repo:
ssh://h...@hg.python.org/devguide . The link is also listed in the
Resources section of the devguide.
On Thu, Jan 20, 2011 at 11:59, s...@pobox.com wrote:
Brett,
I'm sure I just missed it, but where is the devguide in the Subversion tree?
Thx,
Le 17/01/2011 23:41, Nick Coghlan a écrit :
On Tue, Jan 18, 2011 at 6:54 AM, Antoine Pitrou solip...@pitrou.net wrote:
[...]
Also, I see no need to put the maintainers list in the dev guide,
actually.
Every time I see someone syncing the version-independent maintainers
list across branches
Bonus question: if we remove maintainers.rst from py3k, what do we do in
3.1 and 2.7? Iâd favor removing them over keeping outdated versions.
Is there not some advantage to knowing who was the maintainer (or expert)
of a given module at the time of a release?
Eric.
Am 19.01.2011 16:25, schrieb Eric Smith:
Bonus question: if we remove maintainers.rst from py3k, what do we do in
3.1 and 2.7? I’d favor removing them over keeping outdated versions.
Is there not some advantage to knowing who was the maintainer (or expert)
of a given module at the time of
OK, here is my plan that I will implement:
MOVE
--
developers.txt
maintainers.rst
README.gdb
README.coverity
README.Emacs
DELETE (seem way too old to still be relevant; tell me if I am wrong)
---
README.OpenBSD
README.AIX
cheatsheet
LEAVE everything else (with README properly
On Wed, 19 Jan 2011 15:31:24 -0800
Brett Cannon br...@python.org wrote:
OK, here is my plan that I will implement:
MOVE
--
developers.txt
maintainers.rst
README.gdb
README.coverity
README.Emacs
DELETE (seem way too old to still be relevant; tell me if I am wrong)
---
On Wed, Jan 19, 2011 at 15:49, Antoine Pitrou solip...@pitrou.net wrote:
On Wed, 19 Jan 2011 15:31:24 -0800
Brett Cannon br...@python.org wrote:
OK, here is my plan that I will implement:
MOVE
--
developers.txt
maintainers.rst
README.gdb
README.coverity
README.Emacs
DELETE
On Tue, Jan 18, 2011 at 10:17 AM, Brett Cannon br...@python.org wrote:
I am not describing what is in Misc.
It comes down to a question of whether any core dev-specific stuff
should be in Misc that is not a configuration file or not. I say no,
that the directory should contain stuff that
There is a bunch of stuff in Misc that probably belongs in the
devguide (under Resources) instead of in svn. Here are the files I
think can be moved (in order of how strongly I think they should be
moved):
PURIFY.README
README.coverty
README.klocwork
README.valgrind
Porting
developers.txt
Am 17.01.2011 21:32, schrieb Brett Cannon:
There is a bunch of stuff in Misc that probably belongs in the
devguide (under Resources) instead of in svn. Here are the files I
think can be moved (in order of how strongly I think they should be
moved):
PURIFY.README
README.coverty
On Mon, Jan 17, 2011 at 12:32 PM, Brett Cannon br...@python.org wrote:
There is a bunch of stuff in Misc that probably belongs in the
devguide (under Resources) instead of in svn. Here are the files I
think can be moved (in order of how strongly I think they should be
moved):
PURIFY.README
On Mon, 17 Jan 2011 12:32:20 -0800
Brett Cannon br...@python.org wrote:
There is a bunch of stuff in Misc that probably belongs in the
devguide (under Resources) instead of in svn. Here are the files I
think can be moved (in order of how strongly I think they should be
moved):
PURIFY.README
On Tue, Jan 18, 2011 at 6:54 AM, Antoine Pitrou solip...@pitrou.net wrote:
Well it *is* inconvenient in the case of maintainers.rst, which is
often consulted casually for daily bug tracker work. Grepping
Misc/maintainers.rst is much easier than first having to find again
where your checkout
On Jan 17, 2011, at 12:53 PM, Guido van Rossum wrote:
Wow, that Purify file is really old... Unless anyone can confirm it
still works, maybe just toss it? Barry?
Wow indeed. The email address in there hasn't worked in, what? a decade? :)
Toss it!
-Barry
signature.asc
Description: PGP
On Mon, Jan 17, 2011 at 14:41, Nick Coghlan ncogh...@gmail.com wrote:
On Tue, Jan 18, 2011 at 6:54 AM, Antoine Pitrou solip...@pitrou.net wrote:
Well it *is* inconvenient in the case of maintainers.rst, which is
often consulted casually for daily bug tracker work. Grepping
19 matches
Mail list logo
