___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
hi
i face with problem when i run one sample on cygwin:
please help me
Exception happened during processing of request from ('127.0.0.1', 49154)
Traceback (most recent call last):
File /usr/local/lib/python2.5/SocketServer.py, line 222, in handle_request
self.process_request(request,
Hello,
Please ask the support questions at:
http://groups.google.com/group/comp.lang.python
This group is for developing python.
On Wed, Aug 4, 2010 at 12:13 PM, Sarah Hasanlo Nikfar
sara_hasa...@yahoo.com wrote:
hi
i face with problem when i run one sample on cygwin:
please help me
On 04/08/2010 02:08, Steve Holden wrote:
It's a little disappointing to discover that despite the relatively
large number of developers who have received MSDN licenses from
Microsoft, none if us have the time to make sure that the buildbots are
green for the 2.6.6 release.
I wonder if anyone
On 04/08/2010 05:34, Mark Hammond wrote:
On 4/08/2010 11:08 AM, Steve Holden wrote:
It's a little disappointing to discover that despite the relatively
large number of developers who have received MSDN licenses from
Microsoft, none if us have the time to make sure that the buildbots are
green
On Tue, 03 Aug 2010 21:08:31 -0400
Steve Holden st...@holdenweb.com wrote:
It's a little disappointing to discover that despite the relatively
large number of developers who have received MSDN licenses from
Microsoft, none if us have the time to make sure that the buildbots are
green for the
On 04/08/2010 11.36, Tim Golden wrote:
On 04/08/2010 05:34, Mark Hammond wrote:
On 4/08/2010 11:08 AM, Steve Holden wrote:
It's a little disappointing to discover that despite the relatively
large number of developers who have received MSDN licenses from
Microsoft, none if us have the time to
On Wed, Aug 4, 2010 at 11:16, Antoine Pitrou solip...@pitrou.net wrote:
I would advocate a system were people are encouraged to take
responsibility of the problems they introduce when committing changes.
Of course, there are sometimes situations where it's not possible
(triggering
On Wed, Aug 4, 2010 at 7:42 PM, Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Wed, Aug 4, 2010 at 11:16, Antoine Pitrou solip...@pitrou.net wrote:
I would advocate a system were people are encouraged to take
responsibility of the problems they introduce when committing changes.
Of course, there
On 3 August 2010 20:30, Barry Warsaw ba...@python.org wrote:
Brian is looking at Windows now (the buildbots are
a sad and sorry story).
There seems to be something distinctly wrong with the 3.x buildbots. A
lot of test failures and timeouts. At first I assumed it was my
buildslave going flaky
On 8/4/2010 3:49 AM, Tim Golden wrote:
On 04/08/2010 02:08, Steve Holden wrote:
It's a little disappointing to discover that despite the relatively
large number of developers who have received MSDN licenses from
Microsoft, none if us have the time to make sure that the buildbots are
green for
On Wed, Aug 4, 2010 at 8:48 PM, Paul Moore p.f.mo...@gmail.com wrote:
On 3 August 2010 20:30, Barry Warsaw ba...@python.org wrote:
Brian is looking at Windows now (the buildbots are
a sad and sorry story).
There seems to be something distinctly wrong with the 3.x buildbots. A
lot of test
On 8/4/2010 6:08 AM, Nick Coghlan wrote:
On Wed, Aug 4, 2010 at 7:42 PM, Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Wed, Aug 4, 2010 at 11:16, Antoine Pitrou solip...@pitrou.net wrote:
I would advocate a system were people are encouraged to take
responsibility of the problems they introduce
Le mercredi 04 août 2010 à 21:43 +1000, Richard Jones a écrit :
On Wed, Aug 4, 2010 at 8:48 PM, Paul Moore p.f.mo...@gmail.com wrote:
On 3 August 2010 20:30, Barry Warsaw ba...@python.org wrote:
Brian is looking at Windows now (the buildbots are
a sad and sorry story).
There seems to be
On Wed, Aug 4, 2010 at 10:05 PM, Antoine Pitrou solip...@pitrou.net wrote:
It happens when running test_smtplib before test_smtpb:
Aha! Thanks for the clue. I've checked in a fix.
Richard
___
Python-Dev mailing list
Python-Dev@python.org
Hi guys,
there's this 2 year old bug about making strings passed to KeyError round trip:
http://bugs.python.org/issue2651
There are three things I like you to present opinions on.
0. The moratorium.
Based on the old 2.x patch there I created a new one for py3k. It's been
reviewed and it was
On Wed, 4 Aug 2010 15:39:16 +0200
Łukasz Langa luk...@langa.pl wrote:
1. The patch makes KeyError behave analogically to IOError so that the first
arg is now a message and the second is the actual key.
raise KeyError(Key not found, a Scotsman on a horse)
Traceback (most recent call last):
2010/8/4 Łukasz Langa luk...@langa.pl:
1. The patch makes KeyError behave analogically to IOError so that the first
arg is now a message and the second is the actual key.
I agree with Antoine; there's no point to this.
2. Some people suggest adding e.key to KeyError. I like the idea but in my
Hi Giampaolo,
Now that we're in quasi-freeze for 2.6.6 final, this is the kind of change I'd
like to review before backporting. In this case, I'll let it through, but
please check with me first next time.
And thanks for your work!
-Barry
On Aug 04, 2010, at 10:58 AM, giampaolo.rodola wrote:
Is there a way of determining the suffix used after a drive letter to denote a
drive, e.g. on Windows the : in rC:\Dir\Subdir\File.Ext ? Or is the colon
so universal that it is considered unnecessary? Should it be in the os module
somewhere (as far as I can tell, it isn't, although every
On Aug 03, 2010, at 09:08 PM, Steve Holden wrote:
It's a little disappointing to discover that despite the relatively
large number of developers who have received MSDN licenses from
Microsoft, none if us have the time to make sure that the buildbots are
green for the 2.6.6 release.
Should note
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after they commit some changes (or at least
on a regular, say weekly, basis), and so gradually the buildbots have
a tendency to turn from green to red,
It's Windows specific syntax and always a colon. Use
os.path.splitdrive() to parse it. I don't think there's a need to add
a named constant for it (you're the first to ask, in my memory).
On Wed, Aug 4, 2010 at 7:45 AM, Rob Cliffe rob.cli...@btinternet.com wrote:
Is there a way of determining
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after they commit some changes (or at least
on a regular, say weekly, basis), and so gradually the buildbots have
On 04/08/2010 16:15, exar...@twistedmatrix.com wrote:
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after they commit some changes (or at least
on a regular,
On Thu, Aug 5, 2010 at 1:10 AM, Guido van Rossum gu...@python.org wrote:
It's Windows specific syntax and always a colon. Use
os.path.splitdrive() to parse it. I don't think there's a need to add
a named constant for it (you're the first to ask, in my memory).
HI Guido, I'm not a windows user
Thanks for your replies, guys.
As it happens, what sparked the question was trying to determine in a
platform-independent way whether a path consisted of a bare drive
specification (e.g. C:). I guess
os.path.splitdrive(MyPath)[1] ==
takes care of that.
Rob Cliffe
- Original Message
On 4 August 2010 08:49, Tim Golden m...@timgolden.me.uk wrote:
I have watched the buildbot pages occasionally, especially when I see
Windows-related commits going in, but several times red buildbots
have turned out to be -- apparently -- environmental / local issues
unrelated to commits.
On 4 August 2010 13:05, Antoine Pitrou solip...@pitrou.net wrote:
I'm also quite confused by the test_smtpd failures that pop up on some
of the test runs that I've had absolutely no luck reproducing locally
under OS X or Solaris.
It happens when running test_smtplib before test_smtpb:
Nice!
On Aug 04, 2010, at 03:15 PM, exar...@twistedmatrix.com wrote:
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after they commit some changes (or at least
on a
Le mercredi 04 août 2010 à 16:28 +0100, Paul Moore a écrit :
On 4 August 2010 13:05, Antoine Pitrou solip...@pitrou.net wrote:
I'm also quite confused by the test_smtpd failures that pop up on some
of the test runs that I've had absolutely no luck reproducing locally
under OS X or
On 03:17 pm, fuzzy...@voidspace.org.uk wrote:
On 04/08/2010 16:15, exar...@twistedmatrix.com wrote:
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after they
On 8/4/2010 11:00 AM, Brian Curtin wrote:
On Wed, Aug 4, 2010 at 09:48, Barry Warsaw ba...@python.org
mailto:ba...@python.org wrote:
On Aug 03, 2010, at 09:08 PM, Steve Holden wrote:
It's a little disappointing to discover that despite the relatively
large number of developers
On 8/4/2010 11:00 AM, Brian Curtin wrote:
On Wed, Aug 4, 2010 at 09:48, Barry Warsaw ba...@python.org
mailto:ba...@python.org wrote:
On Aug 03, 2010, at 09:08 PM, Steve Holden wrote:
It's a little disappointing to discover that despite the relatively
large number of developers
On 04/08/2010 16:38, Steve Holden wrote:
On 8/4/2010 11:00 AM, Brian Curtin wrote:
On Wed, Aug 4, 2010 at 09:48, Barry Warsawba...@python.org
mailto:ba...@python.org wrote:
On Aug 03, 2010, at 09:08 PM, Steve Holden wrote:
It's a little disappointing to discover that despite the
-Original Message-
From: Martin v. Löwis [mailto:mar...@v.loewis.de]
Sent: 3. ágúst 2010 20:48
To: Kristján Valur Jónsson
Cc: Python-Dev
Subject: Re: [Python-Dev] pickle output not unique
I just wanted to point this out. We'll attempt some local
workarounds
here, but it
On Wed, Aug 4, 2010 at 8:25 AM, Paul Moore p.f.mo...@gmail.com wrote:
However, from my own experience, the Windows buildbot environment is
fairly flaky, and I spend far too much time killing stuck python
processes and VS JIT debugger processes, rather than actually usefully
debugging real
Am 04.08.2010 17:15, schrieb exar...@twistedmatrix.com:
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after they commit some changes (or at least
on a regular,
On Wed, Aug 4, 2010 at 10:49, Tim Golden m...@timgolden.me.uk wrote:
On 04/08/2010 16:38, Steve Holden wrote:
On 8/4/2010 11:00 AM, Brian Curtin wrote:
On Wed, Aug 4, 2010 at 09:48, Barry Warsawba...@python.org
mailto:ba...@python.org wrote:
On Aug 03, 2010, at 09:08 PM, Steve Holden
2010/8/4 Kristján Valur Jónsson krist...@ccpgames.com:
..
Well, it is not _that_ dangerous. It just causes cache misses when they
wouldn't be expected.
But since this has been brought up and dismissed in issue 8738, I won't
pursue this further.
Don't read too much from the dismissal of
On Wed, Aug 4, 2010 at 11:53 AM, Georg Brandl g.bra...@gmx.net wrote:
The hard part is to know *when* to look. As you might have noticed, the
Python test suite does not run in ten seconds, especially on some of the
buildbots -- it can take 1-2 there to complete. So if you look too soon,
you
On 03:31 pm, ba...@python.org wrote:
On Aug 04, 2010, at 03:15 PM, exar...@twistedmatrix.com wrote:
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after they
On 03:53 pm, g.bra...@gmx.net wrote:
Am 04.08.2010 17:15, schrieb exar...@twistedmatrix.com:
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after they commit
On Wed, 04 Aug 2010 16:45:37 -
exar...@twistedmatrix.com wrote:
I don't think it's that hard to take a look at the end of the day (or
before starting anything else the next morning). All it really takes is
a choice on the part of each developer to care whether or not their
changes
Am 04.08.2010 18:45, schrieb exar...@twistedmatrix.com:
How hard is it to look at a web page?
The hard part is to know *when* to look. As you might have noticed,
the
Python test suite does not run in ten seconds, especially on some of
the
buildbots -- it can take 1-2 there to complete. So if
Am 04.08.2010 18:21, schrieb David Stanek:
On Wed, Aug 4, 2010 at 11:53 AM, Georg Brandl g.bra...@gmx.net wrote:
The hard part is to know *when* to look. As you might have noticed, the
Python test suite does not run in ten seconds, especially on some of the
buildbots -- it can take 1-2 there
On Aug 04, 2010, at 06:58 PM, Antoine Pitrou wrote:
On Wed, 04 Aug 2010 16:45:37 -
exar...@twistedmatrix.com wrote:
I don't think it's that hard to take a look at the end of the day
(or before starting anything else the next morning). All it really
takes is a choice on the part of each
I don't really have any answer to this problem right now. Is it
possible to set up a local buildslave-like environment (so I can run
the test suite on my development PC without needing to set up access
and register that PC as a temporary buildslave, which wouldn't be
practical for me)? If I
[I've got no response from python-ideas, so I am forwarding to python-dev.]
With addition of fixed offset timezone class and the timezone.utc
instance [0], it is easy to get UTC time as an aware datetime
instance:
datetime.now(timezone.utc)
datetime.datetime(2010, 8, 3, 14, 16, 10, 670308,
http://docs.pythonsprints.com/core_development/beginners.html
Building ssl requires Perl and nasm, and gets completed as a post-build
step. I haven't done that in a while but it's documented in
PCBuild/readme.txt. That's the stuff I'll be adding to the above document.
Perl shouldn't be a
It happens when running test_smtplib before test_smtpb:
Nice! How did you work that out? I'd like to learn how to diagnose
this sort of thing, because it seems to come up a lot, and I'm not
much use at the moment :-)
I simply tried to run test_smtplib before test_smtpd.
A more
On 8/4/2010 12:42 PM, exar...@twistedmatrix.com wrote:
On 03:31 pm, ba...@python.org wrote:
On Aug 04, 2010, at 03:15 PM, exar...@twistedmatrix.com wrote:
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers
On 04/08/2010 18:53, Martin v. Löwis wrote:
It happens when running test_smtplib before test_smtpb:
Nice! How did you work that out? I'd like to learn how to diagnose
this sort of thing, because it seems to come up a lot, and I'm not
much use at the moment :-)
I simply tried
Wiadomość napisana przez Steve Holden w dniu 2010-08-04, o godz. 19:56:
But I see rules being established (there's a language moratorium: no
changes!, no release should be made unless the buildbots are *all*
green) and then ignored apparently on a whim. This doesn't give people
any
On Wed, 04 Aug 2010 13:56:27 -0400
Steve Holden st...@holdenweb.com wrote:
This whole discussion seems to make it clear that the release manager
procedures are still ill-defined in certain areas. Otherwise a release
manager could proceed by reading a web page an even, heaven help us,
On Aug 04, 2010, at 01:56 PM, Steve Holden wrote:
But I see rules being established (there's a language moratorium: no
changes!, no release should be made unless the buildbots are *all*
green) and then ignored apparently on a whim. This doesn't give people
any confidence that the rules actually
On 8/4/2010 3:08 AM, Senthil Kumaran wrote:
Hello,
Please ask the support questions at:
http://groups.google.com/group/comp.lang.python
Some people filter out posts from google because of spam.
Better gmane.comp.python.general at news.gmane.org
or python-list at python.org.
--
Terry Jan
On 4 August 2010 18:42, Martin v. Löwis mar...@v.loewis.de wrote:
I don't really have any answer to this problem right now. Is it
possible to set up a local buildslave-like environment (so I can run
the test suite on my development PC without needing to set up access
and register that PC as a
This whole discussion seems to make it clear that the release manager
procedures are still ill-defined in certain areas.
No. It rather makes clear that people who never had the role of release
manager
Otherwise a release
manager could proceed by reading a web page an even, heaven help us,
On 4 August 2010 15:48, Barry Warsaw ba...@python.org wrote:
Should note that I did try to build Python using my MSDN license for Windows 7
and Visual Studio 2010. I only had an hour or so to attempt it, and did not
succeed, though I think I got as far as trying to properly situate various
Am 04.08.2010 21:03, schrieb Paul Moore:
On 4 August 2010 18:42, Martin v. Löwis mar...@v.loewis.de wrote:
I don't really have any answer to this problem right now. Is it
possible to set up a local buildslave-like environment (so I can run
the test suite on my development PC without needing to
Georg Brandl g.bra...@gmx.net wrote:
The hard part is to know *when* to look. As you might have noticed, the
Python test suite does not run in ten seconds, especially on some of the
buildbots -- it can take 1-2 there to complete.
Based on this and other issues, I don't think it's practical to
On 4 August 2010 20:17, Martin v. Löwis mar...@v.loewis.de wrote:
Ah. It should certainly be possible to set this up locally - you just
need to run a buildbot master as well, either on the same machine
or a different one. The only thing you can't then get is automatic
notifications on
On 8/4/2010 2:57 PM, Martin v. Löwis wrote:
This whole discussion seems to make it clear that the release manager
procedures are still ill-defined in certain areas.
No. It rather makes clear that people who never had the role of release
manager
Otherwise a release
manager could proceed
Am 04.08.2010 17:53, schrieb Georg Brandl:
Am 04.08.2010 17:15, schrieb exar...@twistedmatrix.com:
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after they
2010/8/5 Fred Drake fdr...@acm.org:
2010/8/4 Łukasz Langa luk...@langa.pl:
1. The patch makes KeyError behave analogically to IOError so that the first
arg is now a message and the second is the actual key.
I agree with Antoine; there's no point to this.
2. Some people suggest adding e.key
On Wed, 04 Aug 2010 23:53:22 +0200
Georg Brandl g.bra...@gmx.net wrote:
The hard part is to know *when* to look. As you might have noticed, the
Python test suite does not run in ten seconds, especially on some of the
buildbots -- it can take 1-2 there to complete.
That should be 1-2
On Wed, Aug 4, 2010 at 5:57 PM, Nick Coghlan ncogh...@gmail.com wrote:
and use a default message of
'Key not found: %r' % key if the key argument is supplied without an
explicit message
I suspect you meant a default message of
'Key not found: %r' % (key,)
since `key` might be a 1-tuple.
On Thu, Aug 5, 2010 at 8:02 AM, Fred Drake fdr...@acm.org wrote:
On Wed, Aug 4, 2010 at 5:57 PM, Nick Coghlan ncogh...@gmail.com wrote:
and use a default message of
'Key not found: %r' % key if the key argument is supplied without an
explicit message
I suspect you meant a default message of
Am 04.08.2010 20:25, schrieb Barry Warsaw:
On Aug 04, 2010, at 01:56 PM, Steve Holden wrote:
But I see rules being established (there's a language moratorium: no
changes!, no release should be made unless the buildbots are *all*
green) and then ignored apparently on a whim. This doesn't give
Am 04.08.2010 19:56, schrieb Steve Holden:
This whole discussion seems to make it clear that the release manager
procedures are still ill-defined in certain areas.
If you mean to imply that a release manager should care for the stability
of their branch also in between of releases -- I'd love
Wiadomość napisana przez Nick Coghlan w dniu 2010-08-04, o godz. 23:57:
2010/8/5 Fred Drake fdr...@acm.org:
2010/8/4 Łukasz Langa luk...@langa.pl:
1. The patch makes KeyError behave analogically to IOError so that the first
arg is now a message and the second is the actual key.
I agree
Hello fellow Pythoneers and Pythonistas,
The source tarballs and Windows installers for the first (and hopefully only)
Python 2.6.6 release candidate is now available:
http://www.python.org/download/releases/2.6.6/
As usual, we would love it if you could download, install, and test these
On 8/4/2010 6:09 PM, Nick Coghlan wrote:
On Thu, Aug 5, 2010 at 8:02 AM, Fred Drakefdr...@acm.org wrote:
On Wed, Aug 4, 2010 at 5:57 PM, Nick Coghlanncogh...@gmail.com wrote:
and use a default message of
'Key not found: %r' % key if the key argument is supplied without an
explicit message
On Thu, 5 Aug 2010 07:57:07 +1000
Nick Coghlan ncogh...@gmail.com wrote:
+1 on what Fred said (i.e. post-moratorium, add a keyword-only key
argument to KeyError, set e.key only if that argument is supplied,
update the standard library to supply it and use a default message of
'Key not found:
On 8/4/2010 6:11 PM, Georg Brandl wrote:
Am 04.08.2010 19:56, schrieb Steve Holden:
This whole discussion seems to make it clear that the release manager
procedures are still ill-defined in certain areas.
If you mean to imply that a release manager should care for the stability
of their
James Mills wrote:
Windows
is one of the only Operating Systems with a File system that reuiqres
this [A-Z]:\ syntax.
There's also VMS, but it uses a colon too. Also its
pathnames are funky enough in other ways that it
needs its own os-specific pathname routines.
I'm not aware of any system
On Aug 04, 2010, at 06:39 PM, Steve Holden wrote:
I'll see if I can get God to extend it for you.
No need to involve the supernatural Steve! Just approve that PSF grant I
submitted so I can finish my (Python powered of course!) clone army.
I honestly do understand that everyone else works
I was fooling around with Python 3.1 today, and I found this little nugget:
import __future__
dir(__future__)
['CO_FUTURE_ABSOLUTE_IMPORT', 'CO_FUTURE_BARRY_AS_BDFL',
'CO_FUTURE_DIVISION', 'CO_FUTURE_PRINT_FUNCTION',
'CO_FUTURE_UNICODE_LITERALS', 'CO_FUTURE_WITH_STATEMENT',
Hello
hmm... BARRY_AS_BDFL and barry_as_FLUFL
Oh, bad consistency. Should have been BARRY_AS_FLUFL and barry_as_flufl.
from __future__ import barry_as_FLUFL
nothing noticable happened.
I made some tests about that and found that the behavior didn’t match
the PEP; I have to redo experiments
On Wed, Aug 4, 2010 at 3:48 PM, Jasper St. Pierre jstpie...@mecheye.net wrote:
I was fooling around with Python 3.1 today, and I found this little nugget:
import __future__
dir(__future__)
['CO_FUTURE_ABSOLUTE_IMPORT', 'CO_FUTURE_BARRY_AS_BDFL',
'CO_FUTURE_DIVISION',
On Aug 04, 2010, at 06:48 PM, Jasper St. Pierre wrote:
hmm... BARRY_AS_BDFL and barry_as_FLUFL
[...]
nothing noticable happened. I googled the latter, and found that it's
an April Fools (of 2009!) checkin that was never reverted.
Wait. It's a joke?!
signature.asc
Description: PGP signature
Greg Ewing writes:
I'm not aware of any system that's just like Windows
except that it uses something other than colons.
It's a shame that Windows machines can be networked; otherwise we
could formally treat drive letters as the scheme component of file
URLs.
Steve Holden writes:
But I see rules being established (there's a language moratorium: no
changes!, no release should be made unless the buildbots are *all*
green) and then ignored apparently on a whim. This doesn't give people
any confidence that the rules actually mean much, and I think
Barry Warsaw ba...@python.org writes:
On Aug 04, 2010, at 06:48 PM, Jasper St. Pierre wrote:
hmm... BARRY_AS_BDFL and barry_as_FLUFL
[...]
nothing noticable happened. I googled the latter, and found that it's
an April Fools (of 2009!) checkin that was never reverted.
Wait. It's a joke?!
Stephen J. Turnbull step...@xemacs.org writes:
It's a shame that Windows machines can be networked
+1 QOTW
Even if QOTW doesn't work in this forum, I still cast my vote.
--
\ “We should strive to do things in [Gandhi's] spirit… not to use |
`\ violence in fighting for our cause, but
2010/8/4 Łukasz Langa luk...@langa.pl:
Shall we do an e.index for IndexErrors as well?
I don't recall stumbling over that need, but the parallel makes it
tempting. I expect is should be a separate patch, though.
Antoine's right about using keyword args from C, though. I'd expect a
new helper
If you mean to imply that a release manager should care for the stability
of their branch also in between of releases -- I'd love to do that,
but I'd need a 36-hour day then.
I'll see if I can get God to extend it for you. I honestly do understand
that everyone else works under the same
88 matches
Mail list logo
