Greg Ewing <[EMAIL PROTECTED]> writes:
> Guido van Rossum wrote:
>
>>>To me, that's an argument in favour of always generating
>>>a .pyc, even for scripts.
>>
>> I'm not sure I follow the connection.
>
> You were saying that if the parser and compiler were
> slow, it would slow down single-file s
[EMAIL PROTECTED] writes:
> In c.l.py Paul Rubin wrote:
>
> Paul> In the old days, it was possible to post stuff to Python's
> Paul> sourceforge pages without logging in. That was turned off for
> Paul> various reasons that weren't bogus, but that didn't strike me as
> Paul> overw
Barry Warsaw <[EMAIL PROTECTED]> writes:
> Let's say something like "string-based exceptions are strongly
> discouraged, and in fact may be deprecated or disappear in a future
> Python version. Use class-based exceptions."
If I have anything to do with it, they _will_ be deprecated in 2.5.
There
Nick Coghlan <[EMAIL PROTECTED]> writes:
> Michael Hudson wrote:
>> (PS: are people still interested in my new-style exceptions patch?
>> http://bugs.python.org/1104669)
>
> Is there a specific concern with it you want people to check out, or just a
> few more &qu
Guido van Rossum <[EMAIL PROTECTED]> writes:
> Dotted non-from imports (e.g. import test.pystone) are rare enough
> that they don't deserve a special rule; if you want me to give a rule,
> I think they should be mixed in with the undotted ones,
> alphabetically.
I actually really hate this style,
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> that *still* won't tell you what precise sources had been used
> to build the binary, as different files simply can be on different
> revisions, and no single number, in whatever way computed, can
> give you full information.
A tangential point is t
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> It stopped counting builds on Windows quite some time ago; perhaps it
> is best to drop the build number entirely?
+1. I don't see how the information it contributes is meaningful in
any way.
Cheers,
mwh
--
Gullible editorial staff continues t
"LD 'Gus' Landis" <[EMAIL PROTECTED]> writes:
> Hi,
>
> So, what does one get when built on a system not connected to
> the net? say from a tarball?
Um, the two things you mention are unrelated. svnversion doesn't
access the network, so the first thing is moot. For the second, we've
talked
Michael Chermside <[EMAIL PROTECTED]> writes:
> So I have a counter-proposal. Let's NOT create a hierarchy of abstract
> base types for the elementary types of Python.
+1
Cheers,
mwh
--
how are the jails in israel?
well, the one I was in was pretty nice
"Fredrik Lundh" <[EMAIL PROTECTED]> writes:
> Checked the python-list archives lately? If you google c.l.python for the
> word "documentation", you'll find recent megathreads with subjects like
> "bitching about the documentation", "opensource documentation problems"
> and "python documentation s
Neal Norwitz <[EMAIL PROTECTED]> writes:
> On 12/23/05, Tim Peters <[EMAIL PROTECTED]> wrote:
>> _assumed_ this was known damage everywhere so was waiting for someone
>> else to fix it ;-) (A parenthentical question: is there a reason you
>> don't pass -uall to regrtest.py?)
>
> It's calling mak
[EMAIL PROTECTED] writes:
> Fredrik> a quit/exit command that actually quits, instead of printing a
> Fredrik> "you didn't say please!" message.
>
> I like Fredrik's idea more and more.
The thing that bothers me about it is that the standard way you tell
python to do something is "call a
"Fredrik Lundh" <[EMAIL PROTECTED]> writes:
> Michael Hudson wrote:
>
>> In other news, clever hacks with tb_next and so on also seem
>> excessive. Why not have the equivalent of "if input.rstrip() ==
>> 'exit': sys.exit()" in the impl
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> Currently, my buildbot isn't connected to IRC at all. If I ever
> enable that aspect, I'll use allowForce=False again to disable
> remotely invoking builds.
#python-dev on freenode is ready and waiting should you decide to
activate this :)
Cheers,
Georg Brandl <[EMAIL PROTECTED]> writes:
> The call to curses.setupterm() leaves my terminal in a bad state.
Hmm.
> The reset program outputs:
> Erase set to delete.
> Kill set to control-U (^U).
> Interrupt set to control-C (^C).
It always says that :) (unless you've messed with stty, I guess)
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> Well, you know that LOAD_CONST only supports 2**31 constants, so
> truncation to int is currently safe (I hope that the compiler detects
> cases where somebody tries to create more than 2**16 constants).
Easy enough to check:
>>> eval(repr(range
Georg Brandl <[EMAIL PROTECTED]> writes:
> Michael Hudson wrote:
>> Georg Brandl <[EMAIL PROTECTED]> writes:
>>
>>> The call to curses.setupterm() leaves my terminal in a bad state.
>>
>> Hmm.
>>
>>> The reset program
Georg Brandl <[EMAIL PROTECTED]> writes:
>> Well, this still has the faint whiff of impossibility about it. Are
>> you sure it's setupterm() that's doing the damage? Can you reproduce
>> interactively?
>
> Yep.
> Alone, the setupterm call [curses.setupterm(sys.__stdout__.fileno())] does
> nothin
Guido van Rossum <[EMAIL PROTECTED]> writes:
> On 1/10/06, Thomas Wouters <[EMAIL PROTECTED]> wrote:
>> Sorry, I missed the point I was aiming at, I guess. I wasn't aiming for
>> fixable bugs; I see these things as, with great effort, holding up your foot
>> at an awkward angle so that it ends up
Gabriel Becedillas <[EMAIL PROTECTED]> writes:
> Hi,
> At the company I work for, we've embedded Python in C++ application we
> develop. Since our upgrade to Python 2.4.2 from 2.4.1 we started hitting
> Py_FatalError("Invalid thread state for this thread") when using debug
> builds.
> We use bo
Donovan Baarda <[EMAIL PROTECTED]> writes:
> I personally think %b would be adding enough. The other suggestions are
> just me being silly :-)
Yeah, the whole area is just crying out for the simplicity and
restraint that is common lisp's #'format function :)
Cheers,
mwh
--
INEFFICIENT CAPIT
Tim Peters <[EMAIL PROTECTED]> writes:
> [Gabriel Becedillas]
>> Can anybody tell me if the patch I suggested is ok ?
>> That will be to add the following code at the end of PyThreadState_Delete:
>>
>> if (autoTLSkey && PyThread_get_key_value(autoTLSkey) == tstate)
>> PyThread_delete_key_valu
"Gregory P. Smith" <[EMAIL PROTECTED]> writes:
> Using BerkeleyDB 3.2 often segfaults for me; using 3.3 often hangs in
> the test suite. Both are so old I don't see much motivation to track
> the issues down.
My goal is to not have http://www.python.org/dev/buildbot/ go red
randomly because of e
BJörn Lindqvist <[EMAIL PROTECTED]> writes:
> [M.-A. Lemburg]
>> I don't see why this is critical for the success of the Path
>> object. I agree with Thomas that interfaces should be made
>> compatible to Path object.
>
> See the steps I mentioned. Unless step #1 is completed there is no way
> to
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> The source distribution would contain aclocal.m4; it would not
> contain the autoconf/autoheader tools themselves.
To a rather different point, do we need aclocal.m4 at all? This is
the log for aclocal.m4:
-
Scott Dial <[EMAIL PROTECTED]> writes:
> So, either the GCC people have not noticed this problem, or (more
> likely) have decided that this is acceptable, but clearly it will cause
> spurious warnings. Hey, after all, they are just warnings.
Well, indeed, but "no warnings" is a useful policy --
Thomas Wouters <[EMAIL PROTECTED]> writes:
> On Wed, Feb 01, 2006 at 11:29:16AM -0500, Tim Peters wrote:
>> [Thomas Wouters]
>> > Well, I said 4.0.3, and that was wrong. It's actually a pre-release of
>> > 4.0.3
>> > (in Debian's 'unstable' distribution.) However, 4.0.2 (the actual release)
>> >
Alex Martelli <[EMAIL PROTECTED]> writes:
> I was recently reviewing a lot of the Python 2.4 code I have written,
> and I've noticed one thing: thanks to the attrgetter and itemgetter
> functions in module operator, I've been using (or been tempted to use)
> far fewer lambdas, particularly but not
Jean-Paul Calderone <[EMAIL PROTECTED]> writes:
> On Fri, 3 Feb 2006 07:00:26 -0800, Alex Martelli <[EMAIL PROTECTED]> wrote:
>>
>>On Feb 3, 2006, at 6:47 AM, Giovanni Bajo wrote:
>>...
>>> use itemgetter and friends but the "correct" way of doing a
>>> defferred "x[1]"
>>> *should* let you wr
Guido van Rossum <[EMAIL PROTECTED]> writes:
> On 2/8/06, Patrick Collison <[EMAIL PROTECTED]> wrote:
>> And to think that people thought that keeping "lambda", but changing
>> the name, would avoid all the heated discussion... :-)
>
> Note that I'm not participating in any attempts to "improve" l
The next PyPy sprint is scheduled to take place right after
PyCon 2006 in Dallas, Texas, USA.
We hope to see lots of newcomers at this sprint, so we'll give
friendly introductions. Note that during the Pycon conference
we are giving PyPy talks which serve well as preparation.
Goals and topi
"Phillip J. Eby" <[EMAIL PROTECTED]> writes:
> At 12:21 PM 2/10/2006 -0800, Guido van Rossum wrote:
>> >PEP 343: The "with" Statement
>>
>>Didn't Michael Hudson have a patch?
>
> PEP 343's "Accepted" status was revert
301 - 332 of 332 matches
Mail list logo
