[Phillip J. Eby]
>> Actually, I started out with "please" -- twice, after having previously
>> asked please in advance. I've also seen lots of messages on Python-Dev
>> where Tim Peters wrote about having wasted time due to other folks not
>> following established procedures, and I tried to emulat
Terry Jones wrote:
> The code below uses a RNG with period 5, is deterministic, and has one
> initial state. It produces 20 different outcomes.
You misunderstand what's meant by "outcome" in this
context. The outcome of your algorithm is the whole
*sequence* of numbers it produces, not each indiv
On Mon, 12 Jun 2006, Giovanni Bajo wrote:
> GetSystemDirectory() is the official way to find the system directory.
You're right. I've added a call to GetSystemDirectory, with a fallback
to the usual locations if it doesn't work.
> Another thing that you might do is to drop those absolute system
Thomas Wouters <[EMAIL PROTECTED]> wrote:
>> It would be an important move towards world peace, if it didn't
>> inspire whole new SCM-holy-wars :-) I have a fair bit of experience with
>> different
>> SCM (VC, source control tool, however you want to call them) so I'll
>> take
>> this opportunity
At 01:36 AM 6/13/2006 +0200, Martin v. Löwis wrote:
> From that, I can only conclude that you requested that people should
>not make changes again without contacting you or the Web-SIG.
Indeed I was -- back when I was under the mistaken impression that PEP 360
actually meant what it appeared to s
Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> Control isn't the issue; it's ensuring that fixes don't get lost or
> reverted from either the external version or the stdlib version.
> Control
> is merely a means to that end. If we can accomplish that via some
> other
> means (e.g. an Externals/ subt
Yes, this is because of the (unfortunate) availability of the dup()
operation. Originally, dup() was only available on Unix, where it's
implemented in the kernel at the file descriptor level: when several
file descriptors all share the same underlying socket, the socket
isn't really closed until th
At 02:00 AM 6/13/2006 +0200, Giovanni Bajo wrote:
>IMO, the better way is exactly this you depicted: move the official
>development
>tree into this Externals/ dir *within* Python's repository. Off that, you can
>have your own branch for experimental work, from which extract your own
>releases, and
It's sounding like a rewording of PEP 360 would help this whole external code issue. If it was changed to say that non-API changes could be directly checked in would that help?That would mean the PEP would list the contact person and what external version corresponds to what Python release. Basic
[Raymond Hettinger]
> I think the note is still useful, but the "rather small" wording
> should be replaced by something most precise (such as the
> value of n=len(x) where n! > 2**19997).
Note that I already removed it, and I'm not putting it back. The
period of W-H was "so short" you could get
[EMAIL PROTECTED] wrote:
> Greg> Multiple values could be written
>
> Greg>case 'a':
> Greg>case 'b':
> Greg>case 'c':
> Greg> ...
>
> That would be an exception to the rule that a line ending in a colon
> introduces an indented block.
Yes, but I don't see th
[EMAIL PROTECTED] wrote:
> Greg> A way out of this would be to define the semantics so that the
> Greg> expression values are allowed to be cached, and the order of
> Greg> evaluation and testing is undefined. So the first time through,
> Greg> the values could all be put in a dict,
At 01:49 AM 6/13/2006 +0200, Martin v. Löwis wrote:
>Phillip J. Eby wrote:
> > This should definitely be explained to authors who are donating
> > libraries to the stdlib, because from my perspective it seemed to me
> > that I was graciously volunteering to be responsible for *all* the work
> > rel
On 6/12/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
At 02:00 AM 6/13/2006 +0200, Giovanni Bajo wrote:>IMO, the better way is exactly this you depicted: move the official>development>tree into this Externals/ dir *within* Python's repository. Off that, you can
>have your own branch for experimenta
Phillip J. Eby wrote:
[...]
> So, to summarize, it's all actually Tim's fault, but only in a parallel
> universe where nobody believes in unit testing. ;-)
>
I'm sorry to contradict you, but every issue of significance is already
known to be Barry's fault.
probably-until-the-end-of-time-ly y'r
On Mon, Jun 12, 2006 at 11:33:49PM +0200, Michael Walter wrote:
> Maybe "switch" became a keyword with the patch..
>
> Regards,
> Michael
>
That's correct.
> On 6/12/06, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> >
> > Could you upload your patch to SourceForge ? Then I could add
> > it to the
> this is mildy insulting, to the people that spent time trying to find
> the best compromises between various issues and keep jython alive.
Sorry, didn't mean to disparage that work.
Bill
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.p
On 6/12/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 02:00 AM 6/13/2006 +0200, Giovanni Bajo wrote:
> >IMO, the better way is exactly this you depicted: move the official
> >development
> >tree into this Externals/ dir *within* Python's repository. Off that, you can
> >have your own branch fo
Ok, here's the summary for the second half of April. My brain is numb
from the setuptools ane PEP 343 discussions, so please have a look
over it and see what I messed up. ;-)
As always, if you have any corrections or comments, please let me know.
=
Announcements
=
-
101 - 119 of 119 matches
Mail list logo
