M.-A. Lemburg writes:
I'd use allowlonesurrogates as name for the surrogates error
handler and lonesurrogatereplace for the utf8b one.
+1
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Stephen J. Turnbull wrote:
Walter Dörwald writes:
surrogatepass (for the don't complain about lone half surrogates
handler) and surrogatereplace sound OK to me. However the other
...replace handlers are destructive (i.e. when such a ...replace
handler is used for encoding, decoding
On Fri, May 8, 2009 at 7:23 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
I have fixed configure by runing autoconf, everything should be fine now
Sorry for the inconvenience.
I am the one responsible for this - I did not realize that the
generated configure/Makefile were also in the trunk,
Hello there. I have sumitted the following patch:
Add an 'offset' argument to zlib.decompress
http://bugs.python.org/issue5804
I'd be interested on getting some more feedback on it.
Kristján
___
Python-Dev mailing list
Python-Dev@python.org
ACTIVITY SUMMARY (05/01/09 - 05/08/09)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
2188 open (+45) / 15604 closed (+30) / 17792 total (+75)
Open issues with patches: 848
On Thu, May 7, 2009 at 18:56, John Arbash Meinel
john.arbash.mei...@gmail.com wrote:
Andrew Bennetts wrote:
Antoine Pitrou wrote:
Robert Kern robert.kern at gmail.com writes:
Since one may have more than one filesystem side-by-side, this can't be
just
be
a system-wide boolean
Brett Cannon wrote:
On Thu, May 7, 2009 at 18:56, John Arbash Meinel
john.arbash.mei...@gmail.com mailto:john.arbash.mei...@gmail.com wrote:
Andrew Bennetts wrote:
Antoine Pitrou wrote:
Robert Kern robert.kern at gmail.com http://gmail.com writes:
Since one may have
On Fri, May 08, 2009 at 09:52:40AM -0700, Brett Cannon wrote:
Thanks for the help to everyone. I ended up simply taking __file__, making
it all uppercase (or lowercase if it is already uppercase) and then doing
os.path.exists() on the modified name. Seems to work.
What if __file__ is on a
On May 4, 2009, at 3:10 AM, Larry Hastings wrote:
I should have brought this up to python-dev before--sorry for being
so slow. It's already in the tracker for a couple of days:
http://bugs.python.org/issue5880
The idea: PyGetSetDef has this void *closure field that acts like
a
A while ago, Guido declared that all special method lookups on
new-style classes bypass __getattr__ and __getattribute__. This almost
completely consistent now, and I've been working on patching up a few
incorrect cases. I've know hit __enter__ and __exit__. The compiler
generates LOAD_ATTR
Casey Duncan wrote:
I think this is an important feature, which allows you to define
generic, reusable getter and setter functions and pass static metadata
to them at runtime. Admittedly I have never needed the full pointer,
my typical usage is to pass in an offset.
I think this should only
Benjamin Peterson wrote:
A while ago, Guido declared that all special method lookups on
new-style classes bypass __getattr__ and __getattribute__. This almost
completely consistent now, and I've been working on patching up a few
incorrect cases. I've know hit __enter__ and __exit__. The compiler
2009/5/8 Terry Reedy tjre...@udel.edu:
2. I am puzzled why those two methods should be extra special, but don't
know enough to say more.
They're not supposed to be special, which is the reason for this
message. :) Currently the interpreter will call __getattr__ when
looking them up. This is not
On Fri, May 8, 2009 at 1:09 PM, Benjamin Peterson benja...@python.orgwrote:
I've know hit __enter__ and __exit__. The compiler
generates LOAD_ATTR instructions for these, so it uses the normal
lookup. The only way I can see to fix this is add a new opcode which
uses _PyObject_LookupSpecial,
2009/5/8 Daniel Stutzbach dan...@stutzbachenterprises.com:
On Fri, May 8, 2009 at 1:09 PM, Benjamin Peterson benja...@python.org
wrote:
I've know hit __enter__ and __exit__. The compiler
generates LOAD_ATTR instructions for these, so it uses the normal
lookup. The only way I can see to fix
2009/5/8 Daniel Stutzbach dan...@stutzbachenterprises.com:
On Fri, May 8, 2009 at 6:14 PM, Benjamin Peterson benja...@python.org
wrote:
Normally special methods use slots of the PyTypeObject struct.
typeobject.c looks up all those methods on Python classes correctly.
In the case of __enter__
Benjamin Peterson wrote:
2009/5/8 Terry Reedy tjre...@udel.edu:
2. I am puzzled why those two methods should be extra special, but don't
know enough to say more.
They're not supposed to be special, which is the reason for this
message. :) Currently the interpreter will call __getattr__ when
Benjamin Peterson wrote:
2009/5/8 Daniel Stutzbach dan...@stutzbachenterprises.com:
On Fri, May 8, 2009 at 6:14 PM, Benjamin Peterson benja...@python.org
wrote:
Normally special methods use slots of the PyTypeObject struct.
typeobject.c looks up all those methods on Python classes correctly.
2009/5/8 Terry Reedy tjre...@udel.edu:
Benjamin Peterson wrote:
2009/5/8 Daniel Stutzbach dan...@stutzbachenterprises.com:
On Fri, May 8, 2009 at 6:14 PM, Benjamin Peterson benja...@python.org
wrote:
Normally special methods use slots of the PyTypeObject struct.
typeobject.c looks up all
19 matches
Mail list logo
