Greg Ewing wrote:
Martin Devera wrote:
Greg, what change do you have in mind regarding that 3 instruction
addition to refcounting ?
I don't have any change in mind. If even an atomic inc
is too expensive, it seems there's no hope for us.
Just from curiosity, would be a big problem
Martin Devera schrieb:
Just from curiosity, would be a big problem removing refcounting and live
with garbage collection only ? I'm not sure if some parts of py code
depends on exact refcnt behaviour (I guess it should not).
Now, this gives a true deja-vu. Python applications often rely on
Steve Holden schrieb:
That links to
http://www.python.org/download/releases/2.5/msi/
which *also* has a block at the top right whose last link is Windows
MSI installer. Unfortunately that takes you to
http://www.python.org/download/releases/2.5/msi/msi
I noticed, but my pyramid
Martin Devera [EMAIL PROTECTED] wrote:
[snip]
Even if you can do fast atomic inc/dec, it forces cacheline with
refcounter to ping-pong between caches of referencing cpus (for read only
class dicts for example) so that you can probably never get good SMP
scalability.
That's ok. Why? Because
Is it an oversight that exception instances do no longer support
slicing in Python 2.5?
This code works in 2.4, but no longer in 2.5:
try:
open(, r)
except IOError, details:
print details[:]
Thomas
___
Python-Dev mailing list
On 9/20/06, Thomas Heller [EMAIL PROTECTED] wrote:
Is it an oversight that exception instances do no longer supportslicing in Python 2.5?This code works in 2.4, but no longer in 2.5:try:open(, r)except IOError, details:
print details[:]Technically, yes. There is no entry in the sq_slice field for
Brett Cannon schrieb:
On 9/20/06, Thomas Heller [EMAIL PROTECTED] wrote:
Is it an oversight that exception instances do no longer support
slicing in Python 2.5?
This code works in 2.4, but no longer in 2.5:
try:
open(, r)
except IOError, details:
print details[:]
Thomas Heller schrieb:
1. The __str__ of a WindowsError instance hides the 'real' windows
error number. So, in 2.4 print error_instance would print
for example:
[Errno 1002] Das Fenster kann die gesendete Nachricht nicht verarbeiten.
while in 2.5:
[Error 22] Das Fenster kann
On 9/20/06, Thomas Heller [EMAIL PROTECTED] wrote:
Brett Cannon schrieb: On 9/20/06, Thomas Heller [EMAIL PROTECTED] wrote: Is it an oversight that exception instances do no longer support
slicing in Python 2.5? This code works in 2.4, but no longer in 2.5: try: open(, r) except IOError, details:
Martin v. Löwis schrieb:
Thomas Heller schrieb:
1. The __str__ of a WindowsError instance hides the 'real' windows
error number. So, in 2.4 print error_instance would print
for example:
[Errno 1002] Das Fenster kann die gesendete Nachricht nicht verarbeiten.
while in 2.5:
Patch / Bug Summary
___
Patches : 419 open ( +3) / 3410 closed ( +2) / 3829 total ( +5)
Bugs: 910 open (+12) / 6185 closed ( +5) / 7095 total (+17)
RFE : 235 open ( +1) / 238 closed ( +0) / 473 total ( +1)
New / Reopened Patches
__
On 9/19/06, Greg Ewing [EMAIL PROTECTED] wrote:
I haven't really thought it through in detail. It
just seems as though it would be a lot less confusing
if you could figure out from static information which
module will get imported by a given import statement,
instead of having it depend on
On 9/17/06, Nick Coghlan [EMAIL PROTECTED] wrote:
One of the biggest issues I have with the current AST is that I don't believe
it really gets the slice and extended slice terminology correct (it uses
'extended slice' to refer to multi-dimensional indexing, but the normal
meaning of that
13 matches
Mail list logo
