Talin schrieb:
> I just posted on the tracker a patch which adds extensive documentation
> for PEP 3101 to the Python Library Reference. This includes:
>
>str.format()
>format()
>__format__
>Formatter
>format string syntax
>format specification mini-language
>
> http://bu
Talin wrote:
> I just posted on the tracker a patch which adds extensive documentation
> for PEP 3101 to the Python Library Reference. This includes:
>
>str.format()
>format()
>__format__
>Formatter
>format string syntax
>format specification mini-language
>
> http://bugs
Two short issues:
* Shouldn't str.decode() be removed? Every call to it says
"TypeError: decoding str is not supported".
* Using e.g. b"abc".find("a") gives "SystemError: can't use str as char buffer".
This should be a TypeError IMO.
Georg
--
Thus spake the Lord: Thou shalt indent with fou
Eric Smith schrieb:
> Talin wrote:
>> I just posted on the tracker a patch which adds extensive documentation
>> for PEP 3101 to the Python Library Reference. This includes:
>>
>>str.format()
>>format()
>>__format__
>>Formatter
>>format string syntax
>>format specification
Georg Brandl wrote:
> Eric Smith schrieb:
>> Talin wrote:
>>> I just posted on the tracker a patch which adds extensive documentation
>>> for PEP 3101 to the Python Library Reference. This includes:
>>>
>>>str.format()
>>>format()
>>>__format__
>>>Formatter
>>>format string syn
On 8/31/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> For me on OS X, I'm still getting a failure in test_plistlib and an
> unexpected skip in test_ssl.
The skip is intentional; the ssl module is in a state of flux, having the
latest changes from the trunk applied, but not adjusted to the new la
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 31, 2007, at 12:52 AM, Guido van Rossum wrote:
> I'm pretty happy where we stand now -- I just squashed the last two
> failing tests (test_mailbox and test_oldmailbox). It is 9:30 pm here
> and I'm tired, so I'm going to try and get a good nigh
Barry Warsaw wrote:
> For me on OS X, I'm still getting a failure in test_plistlib and an
> unexpected skip in test_ssl.
If it helps, the test_plistlib errors follow.
$ ./python.exe Lib/test/test_plistlib.py -v
test_appleformatting (__main__.TestPlistlib) ... ERROR
test_appleformattingfromlit
On 31 Aug 2007, at 02:36, Talin wrote:
...
> Also, I'm interested in suggestions as to any other standard types
> that
> ought to have a __format__ method, other than the obvious Date/Time
> classes. What kinds of things do people usually want to print?
For years I've thought that various collec
>> For me on OS X, I'm still getting a failure in test_plistlib and an
>> unexpected skip in test_ssl.
>
> If it helps, the test_plistlib errors follow.
In case it isn't clear: test_plistlib will fail *only* on OS X, because
it isn't run elsewhere. So somebody with OS X needs to fix it.
Regard
Martin v. Löwis wrote:
>>> For me on OS X, I'm still getting a failure in test_plistlib and an
>>> unexpected skip in test_ssl.
>> If it helps, the test_plistlib errors follow.
>
> In case it isn't clear: test_plistlib will fail *only* on OS X, because
> it isn't run elsewhere. So somebody with
Talin wrote:
> I'm looking for a volunteer who understands the Decimal class well
> enough to write a __format__ method for it. It should handle all of the
> same format specifiers as float.__format__, but it should not use the
> same implementation as float (so as to preserve accuracy.)
>
> Al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 31, 2007, at 7:25 AM, Thomas Wouters wrote:
> On 8/31/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> For me on OS X, I'm still getting a failure in test_plistlib and an
> unexpected skip in test_ssl.
>
> The skip is intentional; the ssl module i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 31, 2007, at 8:17 AM, Eric Smith wrote:
> Martin v. Löwis wrote:
For me on OS X, I'm still getting a failure in test_plistlib and an
unexpected skip in test_ssl.
>>> If it helps, the test_plistlib errors follow.
>>
>> In case it isn't
> Any suggestions?
I've now backed out my first patch, and implemented an extension
to msvcrt, as well as a command line option for regrtest. Let's
see how this works.
Regards,
Martin
___
Python-3000 mailing list
[email protected]
http://mail.pytho
Martin v. Löwis schrieb:
>> Any suggestions?
>
> I've now backed out my first patch, and implemented an extension
> to msvcrt, as well as a command line option for regrtest. Let's
> see how this works.
>
> Regards,
> Martin
At least the tests on the win32 buildbot now do not hang any longer
if I
Will commits still be merged between trunk and py3k in the future
(after the 3.0a1 release), or must this now be down by the developers
themselves?
Or is it less work for the one who does the merge if applicable bug fixes are
comitted to both trunk and py3k branch?
Thomas
___
Please don't submit anything to the py3k branch until I announce it's
unfrozen or I specifically ask you to do something.
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Python-3000 mailing list
[email protected]
http://mail.py
Yes on both accounts. Checkin coming up.
On 8/31/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
> Two short issues:
>
> * Shouldn't str.decode() be removed? Every call to it says
> "TypeError: decoding str is not supported".
>
> * Using e.g. b"abc".find("a") gives "SystemError: can't use str as cha
FWIW I think "s".find(b"b") should also raise a TypeError, but I don't
have the guts to tackle that today.
On 8/31/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Yes on both accounts. Checkin coming up.
>
> On 8/31/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
> > Two short issues:
> >
> > * Shou
I haven't heard yet that merging is impossible or useless; there's
still a lot of similarity between the trunk and the branch.
As long that remains the case, I'd like to continue to do merges
(except for those files that have been completely rewritten or
removed, like README, bufferobject.* or int
The release is available from http://python.org/download/releases/3.0/
I'll send a longer announcement to python-list and
python-announce-list. Please blog about this if you have a blog!
Thanks to all who helped out! It's been a great ride.
--
--Guido van Rossum (home page: http://www.python.or
The branch is now unfrozen. I tagged the release as r30a1.
On 8/31/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Please don't submit anything to the py3k branch until I announce it's
> unfrozen or I specifically ask you to do something.
--
--Guido van Rossum (home page: http://www.python.org
On 8/31/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> On Aug 31, 2007, at 8:17 AM, Eric Smith wrote:
> > Martin v. Löwis wrote:
> For me on OS X, I'm still getting a failure in test_plistlib and an
> unexpected skip in test_ssl.
> >>> If it helps, the test_plistlib errors follow.
> >>
> >
I tried to compile Python 3.0 with MS Visual Studio 2005 on Windows XP
SP2 (German) and I run into multiple problems with 3rd party modules.
The problem with time on German installations of Windows still exists.
It renders Python 3.0a on Windows for Germans pretty useless. :/
* the import of _time
In 3.0a1 on Polish winxp os.stat() raises UnicodeDecodeError (utf-8
codec can't decode ...) if file not exist, it is probably caused by
localized error messages returned by FormatMessage.
--
闇に隠れた黒い力
弱い心を操る
___
Python-3000 mailing list
Python-3000@pytho
Piotr Duda wrote:
> In 3.0a1 on Polish winxp os.stat() raises UnicodeDecodeError (utf-8
> codec can't decode ...) if file not exist, it is probably caused by
> localized error messages returned by FormatMessage.
On German Win XP, too
Christian
___
Pyth
Hello,
Christian Heimes wrote:
> Piotr Duda wrote:
> > In 3.0a1 on Polish winxp os.stat() raises UnicodeDecodeError (utf-8
> > codec can't decode ...) if file not exist, it is probably caused by
> > localized error messages returned by FormatMessage.
>
> On German Win XP, too
Would you please test
Can you guys please put this in the bug tracker too?
On 8/31/07, Amaury Forgeot d'Arc <[EMAIL PROTECTED]> wrote:
> Hello,
> Christian Heimes wrote:
> > Piotr Duda wrote:
> > > In 3.0a1 on Polish winxp os.stat() raises UnicodeDecodeError (utf-8
> > > codec can't decode ...) if file not exist, it is
On 8/31/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > For me on OS X, I'm still getting a failure in test_plistlib and an
> No worry, I cracked it, just in time before the release.
Seeing the recent changes to plistlib does make me think that bytes is
more awkward than it should be.
On 8/31/07, Jim Jewett <[EMAIL PROTECTED]> wrote:
> On 8/31/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>
> > > For me on OS X, I'm still getting a failure in test_plistlib and an
>
> > No worry, I cracked it, just in time before the release.
>
> Seeing the recent changes to plistlib does
Christian Heimes schrieb:
> I tried to compile Python 3.0 with MS Visual Studio 2005 on Windows XP
> SP2 (German) and I run into multiple problems with 3rd party modules.
> The problem with time on German installations of Windows still exists.
Not for me - it works fine here. Are you sure your sou
> (1) Allow bytes methods to take a literal string (which will
> obviously be in the source file's encoding).
To rephrase Guido's comment: do you have the slightest idea on
how to specify and implement that?
Regards,
Martin
___
Python-3000 mailing list
On 8/31/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 8/31/07, Jim Jewett <[EMAIL PROTECTED]> wrote:
> > (1) Allow bytes methods to take a literal string (which will
> > obviously be in the source file's encoding).
> Yuck, yuck about the source file encoding part. Also, there is no way
>
>> Yuck, yuck about the source file encoding part. Also, there is no way
>> to tell that a particular argument was passed a literal.
>
> There is when compiling to bytecode; it goes in co_consts.
>
>> The very
>> definition of "this was a literal" is iffy -- is x a literal when
>> passed to f bel
On 8/31/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> >> Yuck, yuck about the source file encoding part. Also, there is no way
> >> to tell that a particular argument was passed a literal.
> > There is when compiling to bytecode; it goes in co_consts.
> >> The very
> >> definition of "this w
Martin v. Löwis wrote:
> Christian Heimes schrieb:
>> I tried to compile Python 3.0 with MS Visual Studio 2005 on Windows XP
>> SP2 (German) and I run into multiple problems with 3rd party modules.
>> The problem with time on German installations of Windows still exists.
>
> Not for me - it works
On 8/31/07, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Martin v. Löwis wrote:
> > Christian Heimes schrieb:
> >> I tried to compile Python 3.0 with MS Visual Studio 2005 on Windows XP
> >> SP2 (German) and I run into multiple problems with 3rd party modules.
> >> The problem with time on German
How should we replace in our code:
for k,v in dict.iteritems():
with this ??
for k,v in zip(dict, dict.values()):
Sorry if this is the wrong forum for questions like this.
~Sean
___
Python-3000 mailing list
[email protected]
http://mail.python.o
2007/9/1, Sean DiZazzo <[EMAIL PROTECTED]>:
> How should we replace in our code:
>
> for k,v in dict.iteritems():
for k, v in dict.items():
--
Lino Mastrodomenico
E-mail: [EMAIL PROTECTED]
___
Python-3000 mailing list
[email protected]
http://mail
Dear Travis, in my MPI wrappers, I use MPI_Alloc_mem function to get
'special' MPI memory, and next I return it to Python using
return PyBuffer_FromReadWriteMemory(ptr, len);
Well, getting back this rw-buffer in python, I tried to do
mem = MPI.Alloc_mem(10)
mem[:] = str8('\0') * 8 # sort of memz
Guido van Rossum wrote:
> Does this mean that all the problems you reported at the start of this
> thread are gone? (If so, I need to remove the link to this thread from
> the online release notes. :-)
Just the problem with the time module is gone. The problems with the 3rd
party modules still exi
On 8/31/07, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > Does this mean that all the problems you reported at the start of this
> > thread are gone? (If so, I need to remove the link to this thread from
> > the online release notes. :-)
>
> Just the problem with the tim
Jim Jewett wrote:
> On 8/31/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>
> > x = "abc"
> > f(x)
>
> I suppose consistency with that sort of use ... is
> the main argument against this.
I'd be *very* upset if Python started behaving differently
depending on whether I wrote a literal direct
Someone added this comment to my blog
(http://www.artima.com/forums/flat.jsp?forum=106&thread=213583&start=0#278818):
"Only a question please, I have Python 2.5 installed in my windows XP
machine and I would like to install Python 3a1. I think I could have
troubles at the Windows Registry level. D
"Guido van Rossum" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Someone added this comment to my blog
> (http://www.artima.com/forums/flat.jsp?forum=106&thread=213583&start=0#278818):
>
> "Only a question please, I have Python 2.5 installed in my windows XP
> machine and I would
Is there no option in the installer to associate Python with .py, .pyc,
etc.? Obviously then the logical choice would be to unselect that (or
perhaps have it unselected by default for alpha installations).
--
Nick
___
Python-3000 mailing list
Python-3000
> If it works because the bytecode compiler changes x.split(":") into
> the moral equivalent of
>
> try:
> x.split(":")
> except StrNotBytesError:
> x.split(b":")
>
> that is good enough.
And how do you propose to implement that?
Regards,
Martin
_
Jim Jewett wrote:
> I would prefer that x.split(":") work.
>
> If that happens because bytes.split does the conversion for me (so
> that x.split(sep) also works), then great. But I realize that would
> require an assumption about the proper encoding.
If you're going to do things like that, why s
Nicholas Bastin schrieb:
> Is there no option in the installer to associate Python with .py, .pyc,
> etc.?
There certainly is.
> Obviously then the logical choice would be to unselect that (or
> perhaps have it unselected by default for alpha installations).
I'd rather have the user unselect it
50 matches
Mail list logo
