Hi,
this posting - concerning the new turtle module - goes to the Python-Dev
and Python-3000 lists and to a couple of 'power users' of turtle
graphics, hoping to recieve feedback from the developer's point of view
as well as from the user's point of view.
Currently the implementations of the
Hello there.
Yesterday I posted a feature request, http://bugs.python.org/issue3582, along
with a patch.
It provides platform specifict TLS functions on windows.
Implementing it I came across the strange semantics of
PyThread_set_key_value(). If a value has been set previously, it will ignore
t
Is this new as of the last couple of days?
Traceback (most recent call last):
File "/Users/skip/tmp/py/mmfold.py", line 182, in
sys.exit(main())
File "/Users/skip/tmp/py/mmfold.py", line 95, in main
for line in urllib.urlopen(url+"?adminpw=%s" % passwd):
File
[EMAIL PROTECTED] wrote:
> The import statement seems to work from an interactive shell (I have a
> module named test in the same directory as the main prog, hence the
> problem), but even if it does work should we be importing stuff from the
> test package in non-test code?
I saw those checkins g
Thanks for the feedback,
Gregor
Vern Ceder schrieb:
Gregor,
I don't feel authoritative on the correctness/appropriateness of the
implementation, but I do agree completely that behavior b, or what you
have in the 3.0 version, is vastly preferable.
Cheers,
Vern
Gregor Lingl wrote:
Hi,
this
Eric Smith wrote:
Eric Smith wrote:
Eric Smith wrote:
Nick Coghlan wrote:
Secondly, the string % operator appears to have an explicit
optimisation for the 'just return str(self)' case. This optimisation
is missing from the new string format method.
I'll see if I can optimize this case.
3.
Eric Smith trueblade.com> writes:
>
> I finally backported this to 2.6 in r65814. There's a similar 30%
> speedup for the simplest cases. Unicode optimization is worse than
> string optimization, because of the way int, long, and float formatters
> work. This can be fixed, but I'm not sure
> It provides platform specific TLS functions on windows.
In this context, TLS is "thread-local storage".
Bill
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mail
Does anyone have connections with the owners of pythonmac.org?
Apparently they are serving up an ancient version of Python 2.5. The
Google App Engine has a minor issue in 2.5 that's solved in 2.5.1, but
that is apparently not available from that site. Perhaps we can
contribute more recent Mac versi
Guido> Does anyone have connections with the owners of pythonmac.org?
I believe that's Bob Ippolito ([EMAIL PROTECTED] - cc'd).
Skip
Guido> Apparently they are serving up an ancient version of Python
Guido> 2.5. The Google App Engine has a minor issue in 2.5 that's solved
Guido>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 18, 2008, at 12:05 PM, Guido van Rossum wrote:
Does anyone have connections with the owners of pythonmac.org?
Apparently they are serving up an ancient version of Python 2.5. The
Google App Engine has a minor issue in 2.5 that's solved in 2.5
Note that many distros are in the habit of not installing the test
package by default. So dependencies outside that package on *anything*
in it are a problem. Maybe test_support should be lifted out of the
test package?
On Mon, Aug 18, 2008 at 4:35 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> [EM
On Mon, Aug 18, 2008 at 4:35 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
>> The import statement seems to work from an interactive shell (I have a
>> module named test in the same directory as the main prog, hence the
>> problem), but even if it does work should we be imp
On Mon, Aug 18, 2008 at 10:06 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Note that many distros are in the habit of not installing the test
> package by default. So dependencies outside that package on *anything*
> in it are a problem. Maybe test_support should be lifted out of the
> test pa
On Mon, Aug 18, 2008 at 10:34 AM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 18, 2008 at 10:06 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>> Note that many distros are in the habit of not installing the test
>> package by default. So dependencies outside that package on *anything*
>
On Mon, Aug 18, 2008 at 11:10 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 18, 2008 at 10:34 AM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>> On Mon, Aug 18, 2008 at 10:06 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>>> Note that many distros are in the habit of not installing th
Given that we're about to release beta3, I propose to name it
test_support at the top level and leave it at that for now.
Introducing a testing package should be relegated to 3.1 IMO.
On Mon, Aug 18, 2008 at 11:23 AM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 18, 2008 at 11:10 AM, Guid
On Mon, Aug 18, 2008 at 1:31 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Given that we're about to release beta3, I propose to name it
> test_support at the top level and leave it at that for now.
> Introducing a testing package should be relegated to 3.1 IMO.
Why not name it testutils?
-
Brett Cannon python.org> writes:
> >
> > I saw those checkins go by on the checkins list - they have to do with
> > silencing -3 warnings for modules that the stdlib still uses in Python
> > 2.6 for backwards compatibility reasons (but switching to the relevant
> > new approaches in 3.0, thus maki
On Aug 18, 2008, at 2:33 PM, Benjamin Peterson wrote:
Why not name it testutils?
Heh. And what's the difference between *utils, *tools, and *lib?
They all sound the same to me. :-(
-Fred
--
Fred Drake
___
Python-Dev mailing list
Python
On Aug 18, 2008, at 2:43 PM, Antoine Pitrou wrote:
If it's about silencing warnings, then how about putting it in the
warnings
module?
That sounds good to me, and would be very reasonable. This would make
a nice context manager.
-Fred
--
Fred Drake
__
On Mon, Aug 18, 2008 at 11:55 AM, Fred Drake <[EMAIL PROTECTED]> wrote:
> On Aug 18, 2008, at 2:43 PM, Antoine Pitrou wrote:
>>
>> If it's about silencing warnings, then how about putting it in the
>> warnings
>> module?
>
>
> That sounds good to me, and would be very reasonable. This would make a
Alternatively, I just got mail from Bob Ippolito indicating that he'd
be happy to hand over the domain to the PSF. It's got quite a bit more
on it than Python distros, and it's a fairly popular resource for Mac
users I imagine. However macports.org seems to have more Python stuff,
and has a more re
Someone told me the other day that macports made for difficult installs,
but not being a Mac user I wasn't in a position to evaluate the advice.
I can see the desirability of having a Python-specific domain, but then
again if the pydotorg team were going to maintain the content then they
might
The major difference between the packages on macports and
pythonmac.org is that macports is their own distro of nearly
everything, akin to installing a copy of FreeBSD over top of Mac OS X.
pythonmac.org contains packages that are self-contained and don't have
a whole new set of libraries to instal
On Aug 18, 2008, at 5:42 PM, Steve Holden wrote:
Someone told me the other day that macports made for difficult
installs, but not being a Mac user I wasn't in a position to
evaluate the advice.
Not being a Mac user either, I've been using Mac OS X for about a year
now for most of my develo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 18, 2008, at 6:13 PM, Fred Drake wrote:
On Aug 18, 2008, at 5:42 PM, Steve Holden wrote:
Someone told me the other day that macports made for difficult
installs, but not being a Mac user I wasn't in a position to
evaluate the advice.
No
> Guido van Rossum wrote:
>> Alternatively, I just got mail from Bob Ippolito indicating that he'd
>> be happy to hand over the domain to the PSF. It's got quite a bit more
>> on it than Python distros, and it's a fairly popular resource for Mac
>> users I imagine. However macports.org seems to hav
On Mon, Aug 18, 2008 at 3:41 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Aug 18, 2008, at 6:13 PM, Fred Drake wrote:
>
>> On Aug 18, 2008, at 5:42 PM, Steve Holden wrote:
>>>
>>> Someone told me the other day that macports made for difficult
> I strongly recommend that we *NOT* make macports.org the main,
> official Mac OS X version of Python. Secondary is fine, but not
> primary. Macports is what the name says: it's a system of Mac ports of
> Linux packages, mostly command-line only.
I agree with David about this.
> The official Mac
Bill Janssen wrote:
I strongly recommend that we *NOT* make macports.org the main,
official Mac OS X version of Python. Secondary is fine, but not
primary. Macports is what the name says: it's a system of Mac ports of
Linux packages, mostly command-line only.
I agree with David about this.
Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 16, 2008, at 12:52 PM, Brett Cannon wrote:
>On Sat, Aug 16, 2008 at 7:04 AM, Facundo Batista
><[EMAIL PROTECTED]> wrote:
>> Hi!
>>
>> The issue 600362 has two patches (one for 2.6 and the other for 3.0)
>> that are ready to commit (with a small
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everyone,
I am going to try to release the last planned beta of 2.6 and 3.0 this
Wednesday. Looking at the stable buildbots and showstopper bugs indicates
some work to do between now and then. Here are the showstoppers, along with
my recommend
-1 to use mac ports python as the base python
On 18/08/2008, at 22:18, Bill Janssen wrote:
The official Mac Python should be an OS X application, with an icon,
living in /Applications, ideally with a Mac-standard editor app (the
2.5.1 I have has IDLE), etc.
No, probably not. Frankly, I thi
34 matches
Mail list logo
