On 3/5/07, Giovanni Bajo <[EMAIL PROTECTED]> wrote:
> On 05/03/2007 19.46, A.M. Kuchling wrote:
>
> > At PyCon, there was general agreement that exposing a read-only
> > Bazaar/Mercurial/git/whatever version of the repository wouldn't be
> > too much effort, and might make things easier for externa
On 3/6/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Here's a new PEP that's the outgrowth of work Brett Cannon and I did
> at PyCon. Basically we were looking for a way to allow for forward
> compatibilit
On 3/6/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> >> Supported Renamings
> >> ===
> >>
> >> There are at least 4 use cases explicitly supported by this PEP:
> >>
> >> - - Simple top-level package name renamings, such as ``String
On 3/7/07, Titus Brown <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 07, 2007 at 11:10:22AM +0100, "Martin v. L?wis" wrote:
> -> Giovanni Bajo schrieb:
> -> > On 06/03/2007 10.52, Martin v. L?wis wrote:
> -> >
> -> >> I can't see that the barrier at contributing is high.
> -> >
> -> > I think this says
On 3/7/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mar 7, 2007, at 4:36 PM, Brett Cannon wrote:
>
> >> >> Third party package renaming is also supported, via several public
> >>
On 3/7/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mar 7, 2007, at 7:39 PM, Brett Cannon wrote:
>
> >> I think it's important to import on demand only though.
> >
> > And I agree.
>
> C
On 3/8/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> Now that unittest has a test suite, it would seem to make sense that
> it should be fairly high up in the testing order, since most of the
> regression suite depends on it. I'd like to have it included with
> test_grammar, test_opcodes, test_ope
On 3/9/07, Žiga Seilnacht <[EMAIL PROTECTED]> wrote:
> Hi all!
>
> I have just accepted an invitation to become a Python
> developer, so I feel obliged to introduce myself.
>
> My name is Žiga Seilnacht. I'm currently studying civil
> engineering at the University of Ljubljana, Slovenia.
>
Welcome
On 3/9/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> On the subject of datetime enhancements, I came across an SF patch
> (#1673403) the other day that proposed making it possible to compare
> date and datetime objects. Quoting from the patch summary:
>
> """
> Comparing a date to a datetime curre
On 3/9/07, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Collin Winter schrieb:
> > I can't say I'm well-versed in the intricacies of date/time issues,
> > but what you say makes sense. This is exactly why I brought this patch
> > up here : )
>
> Oh h...! Seems like I've opened a can of worms here.
On 3/9/07, André Malo <[EMAIL PROTECTED]> wrote:
> * Brett Cannon wrote:
>
> > On 3/9/07, Christian Heimes <[EMAIL PROTECTED]> wrote:
> > > * What do you think about including PyTz in the Python core? PyTz is
> > > really, REALLY useful when o
On 3/11/07, Patrick Maupin <[EMAIL PROTECTED]> wrote:
> Please forgive me if this has already been discussed -- I only
> recently started paying any attention to this list.
>
> Many versions of python include "new" standard library modules that
> could (or often do already) work fine with previous
On 3/15/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > This particular change looks like gratuitous breakage, no matter how
> > sound the reasons for it, and putting it in to 2.6 with 3.0 "just around
> > the corner" (though not for production purposes) is guaranteed to upset
> > some people
On 3/19/07, Jay Parlar <[EMAIL PROTECTED]> wrote:
> I'm considering applying to be a student in this year's SoC, and the
> AST code generation in particular looks interesting to me (listed
> here: http://wiki.python.org/moin/CodingProjectIdeas/PythonCore).
>
> I was wondering a few things:
>
> 1) W
On 3/19/07, Michael Spencer <[EMAIL PROTECTED]> wrote:
> Jay Parlar wrote:
> > I'm considering applying to be a student in this year's SoC, and the
> > AST code generation in particular looks interesting to me (listed
> > here: http://wiki.python.org/moin/CodingProjectIdeas/PythonCore).
> >
> > I w
On 3/20/07, Facundo Batista <[EMAIL PROTECTED]> wrote:
> People:
>
> At the beginning of March, there was a thread in this list about patchs
> and bugs that teorically weren't checked out.
>
> >From that discussion, I asked myself: "How can I know the temporal
> location of a patch/bug?". Are there
On 3/20/07, Facundo Batista <[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote:
>
> > That's some interesting stuff. Took me a second to realize that the
> > temporal column's total length is the time range from the opening of
> > the oldest bug to the lat
On 3/22/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Sounds good to me. In 3.0 we should probably not have os.popen*(), nor
> the popen2 module at all, and do everything via the subprocess module.
> I wonder if we should even get rid of os.system(); then there should
> be a subprocess.system()
On 3/22/07, Jason Orendorff <[EMAIL PROTECTED]> wrote:
> The lib ref claims that minidom supports DOM Level 1. Does anyone
> know what parts of Level 2 are not implemented? I wasn't able to find
> anything offhand. It seems to be more a matter of what's not
> documented, or what's not covered by
On 3/28/07, Facundo Batista <[EMAIL PROTECTED]> wrote:
> There's this bug (#451607) about the needing of tests for socket SSL...
>
> Last interesting update in the tracker is five years ago, and since a
> lot of work has been done in test_socket_ssl.py (Brett, Neal, Tim,
> George Brandl).
>
> Do yo
On 4/4/07, A.M. Kuchling <[EMAIL PROTECTED]> wrote:
On Wed, Apr 04, 2007 at 04:07:18PM +1000, Anthony Baxter wrote:
> This one was at least personally addressed
> (well, to "Python Contributors"), which is a step ahead of most of
> them.
What gets me is that such surveys are invalid because the
On 4/7/07, Steven Bethard <[EMAIL PROTECTED]> wrote:
On 4/7/07, Steven Bethard <[EMAIL PROTECTED]> wrote:
> Here's a patch implementing collections.counts() as suggested above:
>
> http://bugs.python.org/1696199
>
> Example usage, from the docstring::
>
> >>> items = 'acabbacba'
>
92 $
Last-Modified: $Date: 2007-01-28 21:54:11 -0800 (Sun, 28 Jan 2007) $
Author: Brett Cannon <[EMAIL PROTECTED]>
Guido van Rossum <[EMAIL PROTECTED]>
Status: Final
Type: Standards Track
Content-Type: text/x-rst
Created: 27-Oct-2005
Post-History:
Abstract
In Python 2.4 a
On 4/10/07, Nick Coghlan <[EMAIL PROTECTED]> wrote:
The PEP I checked in for Travis hasn't turned up on the website, despite
building without warnings when I run pep2html.py. The changes I made to
PEP 0 haven't turned up either.
I thought the subversion commit hook for the PEPs folder caused th
This is not the right list to ask for technical support. Please either ask
some place like comp.lang.python or file a bug report.
-Brett
On 4/12/07, Raghuram Devarakonda <[EMAIL PROTECTED]> wrote:
Hi,
I am trying to build latest python on Windows XP and ran into the
following error:
"c1 : f
On 4/16/07, Grig Gheorghiu <[EMAIL PROTECTED]> wrote:
Almost all community buildbots have failed the test step due to a
failure in test_normalization. Here's a link to the community farm for
the trunk:
http://www.python.org/dev/buildbot/community/trunk/
And here's an example of a failure:
ht
On 4/16/07, Grig Gheorghiu <[EMAIL PROTECTED]> wrote:
On 4/16/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> Don't know what suddenly triggered this (nothing I did), but the code
> basically looks correct. What should be happening is regrtest should be
> catching that
On 4/23/07, Darren Dale <[EMAIL PROTECTED]> wrote:
> I was recently searching for some guidance on how to name packages and
> modules, and discovered an inconsistency in the style guides published at
> www.python.org. http://www.python.org/doc/essays/styleguide.html
> says "Module names can be eith
After my import rewrite, I discovered some things that were left out
of both PEP 302 (import hooks) and PEP 328 (absolute/relative
imports). I wanted to run them by everyone before I made the
subsequent changes to the PEPs.
For PEP 302, a loader should raise ImportError if load_module fails
w/o a
On 4/23/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 02:01 PM 4/23/2007 -0700, Brett Cannon wrote:
> >For PEP 302, a loader should raise ImportError if load_module fails
> >w/o an explicit exception being raised.
>
> I'm not sure I understand this; could you p
On 4/23/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 03:16 PM 4/23/2007 -0700, Brett Cannon wrote:
> >The PEP does not explicitly state how to signal that a loader cannot
> >load a module it is asked to. This could happen if someone called a
> >loader withou
On 4/23/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 04:23 PM 4/23/2007 -0700, Brett Cannon wrote:
> >On 4/23/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> > > At 03:16 PM 4/23/2007 -0700, Brett Cannon wrote:
> > > >The PEP does not explicitl
On 4/24/07, Calvin Spealman <[EMAIL PROTECTED]> wrote:
> I have not gotten any replies about this. No comments, suggestions for
> not skipping any missed threads, or corrections. Is everyone good with
> this or should I give it another day or two?
>
Up to you. Usually if anyone is going to reply
On 4/23/07, Collin Winter <[EMAIL PROTECTED]> wrote:
[SNIP - Adding test.test_support.TestCase]
>
> So: any objections to making this change?
God no! I am dying for you to write your replacement for unittest and
get it into the stdlib! I am tired of camelCase method names in all
of my test code.
On 4/24/07, Calvin Spealman <[EMAIL PROTECTED]> wrote:
> Now that I should be able to actually keep up with my summary duties,
> I need to figure out how to tackle the changing landscape of the
> development lists. The old summaries were no problem, before my time.
> When the python-3000 list was c
On 5/1/07, Neal Norwitz <[EMAIL PROTECTED]> wrote:
In rev 54982 (the first time this crash was seen), I see something
which might create a problem. In python/trunk/Modules/posixmodule.c
(near line 6300):
+ PyMem_FREE(mode);
Py_END_ALLOW_THREADS
The PyMem_MALLOC call that creat
ode);
>>Py_END_ALLOW_THREADS
Shouldn't do that.
[Brett Cannon]
> The PyMem_MALLOC call that creates 'mode' is also called without
explicitly
> holding the GIL.
Or that ;-)
Luckily I misread the code so it doesn't do that boo-boo.
Can you call PyMem_FREE()
On 5/6/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Now, why don't we change the semantics as follows: if a file with
matching name
> exists (in import.c::find_module), but opening fails, ImportError is
raised
> immediately with the concrete error message, and without trying the rest
of
>
On 5/12/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
On 5/12/07, Tracker <[EMAIL PROTECTED]> wrote:
[...]
I clicked on the tracker link out of curiosity noticed that the
tracker has been spammed -- issues 1028, 1029 and 1030 are all spam
(1028 seems a test by the spammer).
We know. Skip
On 5/18/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
With the help of Neal Norwitz, Jeremy Hylton, Alex Martelli and Collin
Winter, I've greatly reduced the set of open PEPs numbered less than
3000. Here's a summary. Please speak up if we've made a grave error; I
take all responsibility for t
On 5/18/07, Jeff Rush <[EMAIL PROTECTED]> wrote:
Time is short and I'm still looking for answers to some questions about
cPython, so that it makes a good showing in the Forrester survey.
1) How is the project governed? How does the community make decisions
on what goes into a release?
Y
On 5/18/07, Terry Reedy <[EMAIL PROTECTED]> wrote:
"Stephen J. Turnbull" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
| I think it would be better to do content. URLs come to mind; without
| something clickable, most commercial spam would be hamstrung. But
| few bug reports and
On 5/19/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
Hi,
over the last few weeks I've hacked on a new approach to Python's
documentation.
As Python already has an excellent documentation framework, the docutils,
with a
readable yet extendable markup format, reST, I thought that it should be
poss
For removing extension modules from the build process on Windows, do you
just delete the File entry from PCbuild/pythoncore.vcproj?
-Brett
On 5/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
The Buildbot has detected a new failure of x86 W2k trunk.
Full details are available at:
http://ww
I just want to say thanks for doing this, Michael. __main__.py is IMO
woefully underused and it's great to see Python dogfooding the feature
along with making it easier to explain how to run our unit tests.
On Thu, Dec 2, 2010 at 17:34, michael.foord wrote:
> Author: michael.foord
> Date: Fri Dec
On Sun, Dec 5, 2010 at 14:14, Antoine Pitrou wrote:
> On Sun, 05 Dec 2010 22:48:49 +0100
> "Martin v. Löwis" wrote:
>> I'd like to tighten PEP 11, and declare a policy that systems
>> older than ten years at the point of a feature release are not
>> supported anymore by default. Older systems whe
On Tue, Dec 7, 2010 at 13:57, Eric Smith wrote:
> On 12/07/2010 03:26 PM, Vinay Sajip wrote:
>>
>> I would suggest that when unit testing, rather than adding StreamHandlers
>> to log
>> to stderr, that something like TestHandler and Matcher from this post:
>>
>> http://plumberjack.blogspot.com/201
On Thu, Dec 9, 2010 at 04:26, Thomas Nagy wrote:
> Hello,
>
> I am looking forward to replacing a piece of code
> (http://code.google.com/p/waf/source/browse/trunk/waflib/Runner.py#86) by the
> futures module which was announced in python 3.2 beta. I am a bit stuck with
> it, so I have a few qu
On Thu, Dec 9, 2010 at 16:26, Nick Coghlan wrote:
> On Fri, Dec 10, 2010 at 9:29 AM, Antoine Pitrou wrote:
>> On Thu, 09 Dec 2010 18:10:38 -0500
>> Eric Smith wrote:
>>> If we're looking to reduce the number of methods on str, I wouldn't mind
>>> seeing center() and zfill() also go away, since t
On Fri, Dec 10, 2010 at 22:21, Vinay Sajip wrote:
> Nick Coghlan gmail.com> writes:
>
>
>> This could actually make a reasonably good basic for a "task oriented"
>> subsection of the logging documentation. Something like:
>>
>
> Good suggestion, I'll see what I can do.
Just wanted to +1 on some
For those of you who don't know, the PSF has given me a two month
grant to work on the core. It's mostly focused on the long overdue
overhaul of the dev docs (now being called the devguide) and writing a
HOWTO on porting Python 2 code to Python 3. If I have time left over
it will be spent on the te
To those that want to keep those steps in the dev FAQ, go ahead but I
recuse myself from maintaining it. Having had so many instances of
people asking "how do I do this?" and me almost always able to go
"read the dev FAQ" has basically made me feel like it is not worth the
effort if people are not
On Thu, Jan 6, 2011 at 13:04, Ned Deily wrote:
> In article ,
> brett.cannon wrote:
> [...]
>> summary:
>> Point out that OS X users need to change examples to use python.exe instead
>> of python.
>> Once Python is done building you will then have a working build of Python
>> that can be r
On Sun, Jan 9, 2011 at 00:26, Georg Brandl wrote:
> Am 08.01.2011 23:22, schrieb Antoine Pitrou:
>> On Sat, 08 Jan 2011 23:05:06 +0100
>> brett.cannon wrote:
>>> +For bugs, an issue needs to:
>>> +
>>> +* Clearly explain the bug so it can be reproduced
>>> +* All relevant platform details are inc
On Mon, Jan 10, 2011 at 10:24, Antoine Pitrou wrote:
> On Sun, 9 Jan 2011 15:18:12 -0800
> Brett Cannon wrote:
> >
> > OK, so the sentence is poorly phrased, but in the list of tasks it is
> > labeled explicitly as intermediate when one is comfortable with the
> &g
Tweaked. Will show up in my next push.
On Mon, Jan 10, 2011 at 12:53, Terry Reedy wrote:
>
> +The primary mailing list where discussions about Python's development
>> occur is
>> +python-dev_
>>
>
> suggest adding
> ", mirrored as newsgroup gmane.comp.python.devel."
>
> ...
>
> +python-ideas_.
On Mon, Jan 10, 2011 at 11:44, Antoine Pitrou wrote:
> Le lundi 10 janvier 2011 à 19:37 +, Michael Foord a écrit :
> > On 10/01/2011 19:31, Antoine Pitrou wrote:
> > > Le lundi 10 janvier 2011 à 19:26 +, Michael Foord a écrit :
> > >>>
> > >>> Fair enough. I will remove it.
> > >>>
> > >>
On Tue, Jan 11, 2011 at 19:43, Nick Coghlan wrote:
> On Wed, Jan 12, 2011 at 6:56 AM, brett.cannon
> wrote:
> > +Mailing Lists
> > +'
> > +
> > +You are expected to subscribe to python-committers, python-dev,
> > +python-checkins, and one of new-bugs-announce or python-bugs-list. See
On Mon, Jan 17, 2011 at 12:00, Antoine Pitrou wrote:
> On Sun, 16 Jan 2011 21:38:43 +0100
> brett.cannon wrote:
>> +
>> +Adding to a pre-existing module
>> +---
>> +
>> +If you have found that a function, method, or class is useful and you
>> believe
>> +it would be u
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
maintain
On Mon, Jan 17, 2011 at 12:32, R. David Murray wrote:
> On Mon, 17 Jan 2011 21:00:10 +0100, Antoine Pitrou
> wrote:
>> On Sun, 16 Jan 2011 21:38:43 +0100
>> brett.cannon wrote:
>> > +
>> > +Adding to a pre-existing module
>> > +---
>> > +
>> > +If you have found that
Done
On Mon, Jan 17, 2011 at 15:14, Antoine Pitrou wrote:
> On Mon, 17 Jan 2011 23:37:07 +0100
> brett.cannon wrote:
>> +
>> +To undo a patch, do::
>> +
>> + patch -R -p0 < patch.diff
>> +
>
> Or, simply and more reliably, use the corresponding VCS incantation
> ("svn revert -R ." or "hg reve
On Mon, Jan 17, 2011 at 14:41, Nick Coghlan wrote:
> On Tue, Jan 18, 2011 at 6:54 AM, Antoine Pitrou 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 h
On Tue, Jan 18, 2011 at 05:18, Nick Coghlan wrote:
> On Tue, Jan 18, 2011 at 10:35 PM, Antoine Pitrou wrote:
>> On Tue, 18 Jan 2011 07:14:51 +0100
>> Ezio Melotti wrote:
>>> > +
>>> > +Committing Patches
>>> > +==
>> [...]
>>> > +
>>> > + svnmerge.py merge -r 42
>>> > +
>>> >
On Mon, Jan 17, 2011 at 22:14, Ezio Melotti wrote:
> Hi,
>
> On Thu, Jan 13, 2011 at 12:44 AM, brett.cannon
> wrote:
>>
>> brett.cannon pushed 75300a08c6d7 to devguide:
>>
>> http://hg.python.org/devguide/rev/75300a08c6d7
>> changeset: 88:75300a08c6d7
On Wed, Jan 19, 2011 at 07:01, Simon Cross
wrote:
> On Wed, Jan 19, 2011 at 2:34 PM, Victor Stinner
> wrote:
>> (a) Python 3 doesn't support non-ASCII module names
>
> -0: I'm vaguely against this being supported because I'd rather not
> have to deal with what happens when the guess regarding th
On Wed, Jan 19, 2011 at 10:10, wrote:
>
> Antoine> Ok, thank you but... are you suggesting something or not?
>
> Yes. Keep the vcs command recommendations simple. At least mention idioms
> which likely to apply across a wider range of version control systems.
I was hoping this would flame o
On Wed, Jan 19, 2011 at 10:38, Alexander Belopolsky
wrote:
> On Wed, Jan 19, 2011 at 1:23 PM, Brett Cannon wrote:
> ..
>>>> (a) Python 3 doesn't support non-ASCII module names
> ..
>> -0 from me (unless the Unicode variable naming PEP says otherwise).
>>
On Wed, Jan 19, 2011 at 14:23, Alexander Belopolsky
wrote:
> On Wed, Jan 19, 2011 at 4:40 PM, Terry Reedy wrote:
> ..
>>> For similar reasons we tend to avoid capital letters in module names.
>>
>> That is a stdlib style guide followed by many, but intentionally not
>> enforced.
>
> Indeed. Last
edited and simplified to
only list files with non-obvious names)
On Mon, Jan 17, 2011 at 12:32, Brett Cannon 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 s
On Wed, Jan 19, 2011 at 15:49, Antoine Pitrou wrote:
> On Wed, 19 Jan 2011 15:31:24 -0800
> Brett Cannon wrote:
>> OK, here is my plan that I will implement:
>>
>> MOVE
>> --
>> developers.txt
>> maintainers.rst
>> README.gdb
>> READ
On Wed, Jan 19, 2011 at 15:21, Sandro Tosi wrote:
> Hi,
>
> On Wed, Jan 19, 2011 at 23:19, brett.cannon
> wrote:
>> +Where to Get Help
>> +=
>> +If you are working on Python it is very possible you will come across an
>> issue
>> +where you need some assistance in solving (this
It's just a bit wordy. I simplified it.
On Thu, Jan 20, 2011 at 01:22, Sandro Tosi wrote:
> Hi,
>
> On Thu, Jan 20, 2011 at 04:56, brett.cannon
> wrote:
>> +Unless a name is followed by a '*', you should never assign an issue to
>> +that person, only make them nosy. Names followed by a '*' may
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 wrote:
> OK, here is my plan that I will implement:
>
> MOVE
> --
> developers.txt
>
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, wrote:
>
> Brett,
>
> I'm sure I just missed it, but where is the devguide in the Subversion tree?
>
> Thx,
>
> Skip
>
_
On Thu, Jan 20, 2011 at 12:09, M.-A. Lemburg wrote:
> brett.cannon wrote:
>> Author: brett.cannon
>> Date: Thu Jan 20 20:34:35 2011
>> New Revision: 88127
>>
>> Log:
>> Remove some outdated files from Misc.
>>
>> Removed:
>> python/branches/py3k/Misc/README.AIX
>
> Are you sure that the AIX REA
On Thu, Jan 20, 2011 at 13:09, Alexander Belopolsky
wrote:
> On Thu, Jan 20, 2011 at 3:37 PM, Brett Cannon wrote:
>> On Thu, Jan 20, 2011 at 12:09, M.-A. Lemburg wrote:
> ..
>>>> python/branches/py3k/Misc/cheatsheet
>>>
>>> Wouldn't it be bet
On Thu, Jan 20, 2011 at 16:58, Nick Coghlan wrote:
> On Fri, Jan 21, 2011 at 6:42 AM, brett.cannon
> wrote:
>> brett.cannon pushed 82d3a1b694b3 to devguide:
>>
>> http://hg.python.org/devguide/rev/82d3a1b694b3
>> changeset: 167:82d3a1b694b3
>> user: B
It's the Emacs lovers who put that stuff in all of their files, so I
ain't touching it.
On Thu, Jan 20, 2011 at 13:06, Sandro Tosi wrote:
> Hi,
>
> On Thu, Jan 20, 2011 at 20:33, brett.cannon
> wrote:
>> +..
>> + Local Variables:
>> + mode: indented-text
>> + indent-tabs-mode: nil
>> +
On Fri, Jan 21, 2011 at 18:35, Nick Coghlan wrote:
> Given that some of the dev guide docs cover triaging and other aspects
> of managing issues on the tracker, does it make sense to offer
> devguide checkin access to triagers that want it?
>
There are enough triagers with commit privileges that
http://docs.python.org/devguide/
If you are a core developer and have a correction you want to make you
can simply check out the devguide yourself (link is in the Resources
section of the devguide) and make the corrections yourself. Otherwise
reply here (you can email me directly but I already hav
And I forgot to mention I also plan to edit the help text on the
various fields on the issue tracker to point to the triaging doc.
On Sat, Jan 22, 2011 at 17:08, Brett Cannon wrote:
> http://docs.python.org/devguide/
>
> If you are a core developer and have a correction you want to
On Sat, Jan 22, 2011 at 23:56, Mark Summerfield wrote:
> Hi Brett,
>
> On Sat, 22 Jan 2011 17:08:00 -0800
> Brett Cannon wrote:
>> http://docs.python.org/devguide/
>
> Personally, I found the first paragraph of "Contributing" a bit
> off-putting.
>
>
Bug reports should be filed at bugs.python.org
On Mon, Jan 24, 2011 at 08:39, Stefan Spoettl wrote:
> Using:
> Python 2.7.0+ (r27:82500, Sep 15 2010, 18:14:55)
> [GCC 4.4.5] on linux2
> (Ubuntu 10.10)
> Method to reproduce error:
> 1. Defining a module which is later imported by another:
> --
On Mon, Jan 24, 2011 at 07:33, Nick Coghlan wrote:
> On Mon, Jan 24, 2011 at 9:29 PM, Antoine Pitrou wrote:
>> On Mon, 24 Jan 2011 20:33:07 +1000
>> Nick Coghlan wrote:
>>> On Mon, Jan 24, 2011 at 6:22 AM, Brett Cannon wrote:
>>> >> In "Getting Set U
On Mon, Jan 24, 2011 at 07:46, Antoine Pitrou wrote:
> On Sat, 22 Jan 2011 17:08:00 -0800
> Brett Cannon wrote:
>>
>> Two, what should the final URL be? Georg picked the current one and I
>> am happy with it.
>
> Ditto for me.
>
>> Three, where should it b
On Mon, Jan 24, 2011 at 11:18, Georg Brandl wrote:
> Am 24.01.2011 20:04, schrieb Raymond Hettinger:
>> Looking at http://docs.python.org/dev/library/html.html#module-html it would
>> appear that we've created a new module with a single trivial function.
>>
>> In reality, there was already a pytho
On Mon, Jan 24, 2011 at 17:19, Raymond Hettinger
wrote:
>
> On Jan 24, 2011, at 3:40 PM, Michael Foord wrote:
>> It isn't just unittest, it seems that all *test packages* are in their
>> respective package and not Lib/test except for the json module where Raymond
>> already moved the tests:
>>
>
This broke the buildbots (R. David Murray thinks you may have
forgotten to call super() in the 'payload is None' branch). Are you
getting code reviews and fully running the test suite before
committing? We are in RC.
On Tue, Jan 25, 2011 at 16:39, victor.stinner
wrote:
> Author: victor.stinner
>
On Wed, Jan 26, 2011 at 04:34, Nick Coghlan wrote:
> On Wed, Jan 26, 2011 at 7:57 PM, Victor Stinner
> wrote:
>> I was stupid to not run at least test_email, sorry. And no, I didn't ask
>> for a review, because I thought that such minor change cannot be
>> harmful.
>
> During the RC period, *ever
2011/1/27 Łukasz Langa :
>
> W dniu 2011-01-24 23:13, Benjamin Peterson pisze:
>>
>> I prefer lib2to3 tests to stay in lib2to3/.
>
> On a related note, I had trouble myself with using outdated 2to3 and
> heard complaints about that at least a couple of times. What do we gain
> from bundling 2to3 w
Because of all the writing I have been doing lately, I have been
pulling up a lot of URLs pointing to various Python releases based
around minor versions (e.g., Python 2.7, not specifically 2.7.1). What
has been somewhat annoying is that there are no URLs which act as a
redirect to the latest relea
On Thu, Jan 27, 2011 at 13:21, wrote:
> Brett> Bonus points if we extend this to major versions, too. =)
>
> I know you added a smiley, but just wanted to point out that since Python 2
> and 3 are really different languages, referring 2.4 users to 3.3 might be a
> bad idea. (I imagine it woul
On Thu, Jan 27, 2011 at 13:54, "Martin v. Löwis" wrote:
> Am 27.01.2011 21:38, schrieb Brett Cannon:
>> Because of all the writing I have been doing lately, I have been
>> pulling up a lot of URLs pointing to various Python releases based
>> around minor
On Thu, Jan 27, 2011 at 22:52, Eli Bendersky wrote:
> On Sun, Jan 23, 2011 at 03:08, Brett Cannon wrote:
>> http://docs.python.org/devguide/
>>
>> If you are a core developer and have a correction you want to make you
>> can simply check out the devguide yoursel
On Thu, Jan 27, 2011 at 20:55, Eli Bendersky wrote:
> I'm working on improving the .rst documentation of test.support (Issue
> 11015), and came upon the undocumented "fcmp" function that's being
> exported from test.support, along with a "FUZZ"constant.
>
> As I search through the tests (py3k trun
On Mon, Jan 31, 2011 at 04:43, Antoine Pitrou wrote:
> On Mon, 31 Jan 2011 00:08:25 -0800
> Guido van Rossum wrote:
>>
>> (Basically I am biased to believe that stat() is a pretty slow system
>> call -- this may just be old NFS lore though.)
>
> I don't know about NFS, but starting a Python inter
On Wed, Feb 2, 2011 at 11:48, Éric Araujo 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.
>>>
>>
all fixed
On Wed, Feb 2, 2011 at 03:04, Sandro Tosi wrote:
> On Wed, Jan 26, 2011 at 23:20, brett.cannon
> wrote:
>> +The in-development branch is where new functionality and semantic changes
>
> new functionalities (dunno if it's plural in english or not)?
>
>> +occur. Currently this branch is
On Thu, Feb 3, 2011 at 15:10, Nick Coghlan wrote:
> On Fri, Feb 4, 2011 at 8:01 AM, brett.cannon
> wrote:
>> +Stop Using :mod:`doctest`
>> +'
>> +While 2to3 tries to port doctests properly, it's a rather tough thing to
>> do. It
>> +is probably best to simply convert you
2101 - 2200 of 3314 matches
Mail list logo
