[issue8565] Always run regrtest.py with -bb

[Florent Xicluna]

Florent Xicluna  added the comment:

+1 to force -bb on buildbots
-1 to hack regrtest.

IMHO it should be added to ./Makefile.pre.in and PCbuild/rt.bat, like other 
warning switches ( "-Wd" "-tt" "-3").

--
nosy: +flox
type:  -> feature request

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8565] Always run regrtest.py with -bb

[STINNER Victor]

STINNER Victor  added the comment:

> +1 to force -bb on buildbots

I think that it's already enabled, but I'm not sure.

> -1 to hack regrtest

Does someone use runtests.sh? We should maybe improve this script instead of 
regrtest.py.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8523] shutil.rmtree and os.listdir cannot recover on error conditions

[Tarek Ziadé]

Tarek Ziadé  added the comment:

The whole error handling in rmtree strikes me as something that cannot be used 
efficiently. (see also #7969).

How can you decide in an isolated function, that can be called anywhere in the 
tree you want to remove, the proper thing to do ? You don't know the global 
status of what is going on. 

I think rmtree() should drop these onerror calls and have two different 
behaviors:

1/ remove all it can in the tree, and return a list of files it couldn't 
remove, with the error for each file. The developer can then act upon.

2/ analyze the tree to see if the full removal can be done. If it's possible, 
it does it, if not, it doesn't do anything and return the problems.


For 2/ a possible way to do it could be to copy in a temporary place files that 
are being removed and copy them back in place in case a problem occurs. This 
can be long and space consuming though, for big files and big trees. I am not 
100% sure 2/ is really useful though...

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7834] socket.connect() no longer works with AF_BLUETOOTH L2CAP sockets

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Committed in r80610. Thanks!

--
resolution:  -> fixed
stage: needs patch -> committed/rejected
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8567] decimal module doesn't respect precedence rules for exceptional conditions

[Mark Dickinson]

New submission from Mark Dickinson :

http://speleotrove.com/decimal/daexcep.html specifies a precedence for decimal 
exceptional conditions (scroll right to the bottom of the page):

"""The Clamped, Inexact, Rounded, and Subnormal conditions can coincide with 
each other or with other conditions. In these cases then any trap enabled for 
another condition takes precedence over (is handled before) all of these, any 
Subnormal trap takes precedence over Inexact, any Inexact trap takes precedence 
over Rounded, and any Rounded trap takes precedence over Clamped.""" 

Currently the decimal module doesn't follow this.  For example, the following 
should raise decimal.Overflow, not decimal.Inexact:

Python 3.2a0 (py3k:80609, Apr 29 2010, 11:46:22)
[GCC 4.2.1 (SUSE Linux)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from decimal import *
>>> getcontext().traps[Inexact] = True
>>> Decimal('1e100').exp()
Traceback (most recent call last):
  File "", line 1, in 
  File "/home/dickinsm/Source/py3k/Lib/decimal.py", line 3002, in exp
ans = ans._fix(context)
  File "/home/dickinsm/Source/py3k/Lib/decimal.py", line 1658, in _fix
context._raise_error(Inexact)
  File "/home/dickinsm/Source/py3k/Lib/decimal.py", line 3866, in _raise_error
raise error(explanation)
decimal.Inexact: None


It's also not clear to me exactly which flags should be set in a case like this.

--
assignee: mark.dickinson
messages: 104484
nosy: mark.dickinson
priority: normal
severity: normal
status: open
title: decimal module doesn't respect precedence rules for exceptional 
conditions
type: behavior
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8567] decimal module doesn't respect precedence rules for exceptional conditions

[Mark Dickinson]

Changes by Mark Dickinson :


--
nosy: +facundobatista, rhettinger, skrah

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8568] Test issue

[Mark Dickinson]

New submission from Mark Dickinson :

Test issue:  I just got a 'there was a problem with your submission: tracker 
maintainers informed' message when submitting issue 8567, though it looks as 
though the submission succeeded.

Here's a test issue to try to reproduce.

Steps taken:

Click on "Create New" in the Issues menu.
Enter title and nosy fields;  all other fields left unspecified.
In nosy list, specify: "skrah,rhettinger,facundo.batista"  (note that the last 
entry is misspelled;  it should be "facundobatista").

Hit "Submit New Entry".

This takes me to a new page (URL http://bugs.python.org/issue) with the message:

"""
An error has occurred

A problem was encountered processing your request. The tracker maintainers have 
been notified of the problem.
"""

After hitting the back button in my browser (Firefox) and trying 'Submit New 
Entry' again I get the 'Your request is being processed.  Please be patient' 
message.)

Correcting the nosy list allows the submission to go through.

--
messages: 104485
nosy: facundobatista, mark.dickinson, rhettinger, skrah
priority: normal
severity: normal
status: open
title: Test issue

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8568] Test issue

[Mark Dickinson]

Changes by Mark Dickinson :


--
resolution:  -> invalid
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7511] msvc9compiler.py: ValueError: [u'path']

[R. David Murray]

R. David Murray  added the comment:

Some committers have been using 'resolution: accepted' as a way to mark issues 
that are definitely going to be fixed/enhancement added.  For a critical bug I 
think this is a bit redundant (it is more useful for feature requests), but I'm 
pretty sure Tarek did it on purpose.

--
nosy: +r.david.murray
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4186] type() doesn't accept bases and dict keyword arguments

[R. David Murray]

R. David Murray  added the comment:

Seems reasonable.

--
nosy: +r.david.murray
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2810] _winreg.EnumValue sometimes raises WindowsError ("More data is available")

[R. David Murray]

R. David Murray  added the comment:

How much would increasing the loop count slow down the test?  Since if the bug 
isn't present the loop will run to the end every time, if it is non-trivial it 
would probably be better to keep it shorter, since Brian said it failed one way 
or another 9 out of 10 times.  Either way, a note in the test that it may 
occasionally pass even if the bug is present, but should fail most of the time, 
would be a good idea.

--
nosy: +r.david.murray

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8523] shutil.rmtree and os.listdir cannot recover on error conditions

[rubenlm]

rubenlm  added the comment:

Do you really need the global status? I wrote an onerror that seems to works 
fine after I modified rmtree with the "return" suggested by r.david.murray. It 
assumes that: 

if os.listdir fails: the user doesn't have read permissions in the dir;
if os.remove or os.rmdir fails: the user doesn't have write permissions in the 
dir that contains the file/dir being removed.

There are other reasons it can fail (attributes, acl, readonly filesystem, ...) 
but having access to the global status doesn't seem to be of much help anyway.

I don't like your fix 2/ because it can fail to copy files if you don't have 
read permissions for the file but have write permissions in the directory (so 
you can delete the file). Besides, the behaviour doesn't seem useful.

/1 seems ok to me but to make use of the global status it provides the user 
must write a somewhat complex recovery code.

All in all it seems the current behaviour of having an onerror function is more 
user friendly.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1054967] bdist_deb - Debian packager

[Barry A. Warsaw]

Barry A. Warsaw  added the comment:

Hi Andrew,

Yes, I've played with sdist_dsc, and it's nice in that it takes a 
non-Debianized source tree and turns it into a source package that can be 
uploaded.  What I'm looking for is something that can take a non-Debianized 
source tree and turn it into a native package, essentially by pre-filling a 
debian/ directory like dh_make does, but including additional metadata 
available in the setup.py.

I've started taking a crack at this:

https://launchpad.net/setupdebian

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8084] pep-0370 on osx duplicates existing functionality

[Ronald Oussoren]

Ronald Oussoren  added the comment:

I'd prefer to have this resolved before the next 2.7 beta.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8567] decimal module doesn't respect precedence rules for exceptional conditions

[Mark Dickinson]

Changes by Mark Dickinson :


--
stage:  -> unit test needed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8523] shutil.rmtree and os.listdir cannot recover on error conditions

[Tarek Ziadé]

Tarek Ziadé  added the comment:

> /1 seems ok to me but to make use of the global status it provides 
> the user must write a somewhat complex recovery code.

The onerror() code you did is as complex as a global function working with a 
sequence returned by rmtree, since it is used *everywhere* in rmtree, and not 
only for os.listdir issues. IOW, if you didn't handle other possible failures 
than os.listdir errors, it will fail if rmtree calls it for other APIs like 
os.remove, etc..

If we state that onerror() is not used as a fallback in rmtree(), and do 
whatever it wants to do on its side, in an isolated manner, then I find it 
simpler that this function works will a list of paths rmtree() failed to 
removed, at the end of the rmtree() process. 

I'd be curious to see your onerror() function btw: if it's here just to silent 
permission errors, 1/ would make it even simpler: don't deal with the error 
list returned by rmtree() that's all.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8084] pep-0370 on osx duplicates existing functionality

[Tarek Ziadé]

Changes by Tarek Ziadé :


--
priority: normal -> high

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7511] msvc9compiler.py: ValueError: [u'path']

[Tarek Ziadé]

Tarek Ziadé  added the comment:

Yes I used 'accepted' to mark this issue as something I am working on.

I am confused about the resolution flag, I think it is a bit overlapping with 
the status flag, and overcomplex. 

Maybe we should replace "closed" with various flags like: "fixed", "wontfix",  
"rejected". (My 2 cents of course ;) )

--
resolution: accepted -> 

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8567] decimal module doesn't respect precedence rules for exceptional conditions

[Mark Dickinson]

Mark Dickinson  added the comment:

Regarding the flags that should be set, the relevant portion of the 
specification is at the top of the page mentioned above:

"""
For each condition, the corresponding signal in the context is given, along 
with the defined result. The value of the trap-enabler for each signal in the 
context determines whether an operation is completed after the condition is 
detected or whether the condition is trapped and hence not necessarily 
completed (see IEEE 754 §7 and §8).
"""

Reading between the lines, I think this means that it's okay for an exception 
resulting from a trap to leave the flag state undefined, at least for those 
flags that would have been raised by the operation.  (But flags that were 
already set before the operation should remain set;  while flags corresponding 
to the signals that would not have been raised by the operation should not be 
changed.)

Section 8 if IEEE 754 backs this up to some extent.  Python's decimal traps 
effectively provide what IEEE 754 section 8.3 calls "Immediate transfer 
associated with a block", a form of "immediate exception handling".  Note 2 in 
that section says:

"""
[...] If the indicated exception is signaled in the associated block, causing 
execution of the handler block or transfer of control, then the state of the 
corresponding status flag might not be deterministic.
"""

This doesn't *exactly* apply here, since it's really talking about a sequence 
of primitive operations rather than a single primitive operation, but it's 
close.  (One might reasonably ask that primitive operations be regarded as 
atomic, so act as though all relevant flags are set, and only *then* are any 
relevant traps raised.  This would not be a trivial change, however.)

In spite of this indeterminacy, it would still be nice to have clear rules 
about what Python's decimal module actually does, even if those rules are only 
for developer consumption.

The simplest (and closest to what's already implemented) would be the following:

- any particular operation (i.e. operands + function) determines uniquely some 
set of signals;  the decimal specification gives us an ordering on those 
signals.

- the result of the operation should be as if we go through those signals 
one-by-one in order, and for each signal:

   (a) if the signal is trapped, raise the corresponding exception
   (b) else set the corresponding flag, and move on to the next signal.

Example to clarify these rules: the overflow example above produces the signals 
[Overflow, Inexact, Rounded] in that order.  If 'Overflow' is trapped, the 
Overflow exception is raised and no flags are set.  Otherwise, if 'Inexact' is 
trapped, the Inexact exception is raised and the 'Overflow' flag is set.  
Otherwise, if 'Rounded' is trapped, the Rounded exception is raised and the 
'Overflow' and 'Inexact' flags will have been set.  Otherwise, no exception is 
raised and all three flags are set.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8567] decimal module doesn't respect precedence rules for exceptional conditions

[Mark Dickinson]

Mark Dickinson  added the comment:

Raising priority:  I'd like to get the precedence fix into 2.7.

--
priority: normal -> high

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8569] Upgrade OpenSSL in Windows builds

[Antoine Pitrou]

New submission from Antoine Pitrou :

I don't know how official installers are built, but the standard build 
procedure with the Visual Studio files uses a custom checkout of OpenSSL 
0.9.8l. OpenSSL is now at version 1.0.x, which adds security fixes and 
improvements.

I'd suggest upgrade the "custom checkout" to use the latest OpenSSL version, at 
least for dev branches (it may be too disruptive for the bugfix branches, since 
OpenSSL seems to have a history of changing behaviour a bit even between what 
look like minor versions). I don't have an idea how to do this myself, Linux 
being my development platform.

--
components: Build, Windows
messages: 104496
nosy: brian.curtin, christian.heimes, loewis, pitrou, tim.golden
priority: normal
severity: normal
status: open
title: Upgrade OpenSSL in Windows builds
type: behavior
versions: Python 2.7, Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8569] Upgrade OpenSSL in Windows builds

[Jean-Paul Calderone]

Jean-Paul Calderone  added the comment:

http://www.openssl.org/news/secadv_20100324.txt
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3555

New Windows builds of any versions of CPython which are still receiving 
security updates should be released.

--
nosy: +exarkun
priority: normal -> critical

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7852] [PATCH] Drop "Computer" from "Apple Computer" in plistlib

[Ronald Oussoren]

Ronald Oussoren  added the comment:

test failures have been fixed a while back.

--
resolution:  -> fixed
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2810] _winreg.EnumValue sometimes raises WindowsError ("More data is available")

[Daniel Stutzbach]

Daniel Stutzbach  added the comment:

In the updated patch I uploaded yesterday, I increased the loop count from 100 
to 1000 and it still runs virtually instantly.  I also added a comment stating 
that the test is trying to trigger a race condition.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8476] build-installer fix for setIcon when no script path specified

[Ronald Oussoren]

Ronald Oussoren  added the comment:

The patch looks good, I will apply it over the weekend.

Thanks for looking into this.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8510] update to autoconf2.65

[Matthias Klose]

Matthias Klose  added the comment:

> You don't need to add source in case of 
>   AC_COMPILE_IFELSE([AC_LANG_SOURCE([[]])] .. 
> when the the test is ..main() { return 0 ;} ...

is there a version of the cross configure patch for 3.x?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8567] decimal module doesn't respect precedence rules for exceptional conditions

[Stefan Krah]

Stefan Krah  added the comment:

Mark,

I'm very short of time today, so I hope I don't miss anything that you
wrote.

The model of decNumber (and libmpdec) is to accumulate any status
(flags) that occurs in a function, regardless of whether a signal
is trapped or not. 

Only at function exit the traps are checked. If multiple exceptions
could be raised, the order of precedence applies. All status that
has been accumulated in the function remains in the context.


This would be backed up by:

http://speleotrove.com/decimal/damodel.html

  ==>  flags and trap-enablers:

  ==> "For each of the signals, the corresponding flag is set to 1
   when the signal occurs. It is only reset to 0 by explicit
   user action."


So, in your example, in cdecimal I get:
>>> from cdecimal import *
>>> getcontext().traps[Inexact] = True
>>> Decimal('1e100').exp()
Traceback (most recent call last):
  File "", line 1, in 
cdecimal.Overflow: [, ]


In the square brackets I list all signals that occurred _and_ are
trapped.





 

  "

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8567] decimal module doesn't respect precedence rules for exceptional conditions

[Mark Dickinson]

Mark Dickinson  added the comment:

Thanks, Stefan.  The cdecimal and decnumber behaviour sounds like the ideal one 
to me.

I'm not sure how easy it would be to adopt this behaviour for decimal: it could 
require some significant rewriting, so we may have to leave decimal as it is 
and call the flag situation undefined.

I'll take a proper look sometime (soon, I hope);  Decimal._fix is the main 
place that's going to need fixes.  The hard part is tracking down all the other 
places where a signal is raised.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8540] Make Context._clamp public in decimal module

[Stefan Krah]

Stefan Krah  added the comment:

> Were you thinking of any deviations in particular?

More or less a commentary on what is listed here:

http://speleotrove.com/decimal/dascope.html

  ==> Restrictions


I only have a draft of IEEE754, but for instance I can't find a power
or remainder-near function there.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8535] passing optimization flags to the linker required for builds with gcc -flto

[Marc-Andre Lemburg]

Marc-Andre Lemburg  added the comment:

Matthias Klose wrote:
> 
> Matthias Klose  added the comment:
> 
>> It's probably better to just pass OPT to the linker instead.
> 
> not enough, because -fno-strict-aliasing might be passed in BASE_CFLAGS.

Shouldn't -fno-strict-aliasing be added to OPT instead of
BASE_CFLAGS ? After all, it's an optimization settings.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1644818] Allow built-in packages and submodules as well as top-level modules

[Nick Coghlan]

Nick Coghlan  added the comment:

OK, reassessing with brain fully engaged this time: the current patch is 
incorrect, and this request is more complicated than one might initially think 
:)

It appears that since the patch was originally tried out only on Windows, a 
Modules/Setup based system based system like mine can't even build a patched 
tree. The current incarnation of the Modules/makesetup script won't allow the 
use of a dotted name for a module named in Modules/Setup.

Anyway, I'm uploading a more fleshed out test case which explicitly details 
some of the module namespace invariants that built-in packages would need to 
support (and changing the issue type and title accordingly).

Even beyond these stricter tests, pkgutil and importlib would need to be 
checked to make sure they also support the new behaviour. 

Since I can't build the patch as it currently stands, I don't know how well it 
actually fairs against the stronger set of invariants. However, just looking at 
the patch I'm pretty confident that it doesn't include the necessary work to 
make sure that the parent package actually looks like a package from the 
interpreter's point of view.

--
components:  -Build
stage:  -> needs patch
title: Allow importing built-in submodules -> Allow built-in packages and 
submodules as well as top-level modules
type: behavior -> feature request
versions:  -Python 2.6, Python 2.7, Python 3.1
Added file: http://bugs.python.org/file17126/test_builtin_submodule.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1644818] Allow built-in packages and submodules as well as top-level modules

[Nick Coghlan]

Changes by Nick Coghlan :


--
stage: needs patch -> 

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1644818] Allow built-in packages and submodules as well as top-level modules

[Nick Coghlan]

Nick Coghlan  added the comment:

Unassigning - this idea needs a lot more specification work to be done before 
actually implementing it becomes a good idea.

(e.g. IronPython and Jython should be looked at to see how they handle the 
naming schemes in the standard libraries for their respective runtime 
environments)

--
assignee: ncoghlan -> 

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8523] shutil.rmtree and os.listdir cannot recover on error conditions

[R. David Murray]

R. David Murray  added the comment:

Well, I don't think removing the current onerror support is a viable option for 
backward compatibility reasons, so we might as well fix it.  

I agree that (2) sounds tricky to get reliably right, while I don't see how (1) 
is an improvement over onerror.  It seems to me that the list is either really 
a tree, in which case the error handler has to reimplement most of rmtree's 
logic in order to do a recover, or it is a list of error filepath pairs, in 
which case the error handler would be in most cases simply be iterating over 
the list and branching based on the error flag...which is no different than 
what onerror allows, but onerror doesn't need the loop code.  Actually, it's 
less capable than what onerror allows, since if onerror successfully removes a 
problem file, rmtree will remove the directory, whereas a (1) style handler 
will have to have its own error logic for dealing with the successive removals 
(and the (1) style list will have to be guaranteed to be sorted in the correct 
bottom up order).

I guess I don't see how knowing the global state (which in this case appears to 
mean the total list of files and directories where removal failed) is useful 
very often, if ever.  It feels like it is a more complicated API that provides 
little benefit.  Do you have some use cases in mind, Tarek?

On the other hand, it seems to me that a nice improvement to onerror would be 
for it to accept an object, and call an error-case-specific method for each 
different error case, perhaps even checking for method existence first and 
doing its normal error handling for that case if the method isn't defined.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8523] shutil.rmtree and os.listdir cannot recover on error conditions

[rubenlm]

rubenlm  added the comment:

Here is my current error handler:

def handleRmtreeError(func, path, exc):
  excvalue = exc[1]
  if excvalue.errno == errno.EACCES:
if func in (os.rmdir, os.remove):
  parentpath = path.rpartition('/')[0]
  os.chmod(parentpath, stat.S_IRWXU) # 0700
  func(path)
elif func is os.listdir:
  os.chmod(path, stat.S_IRWXU) # 0700
  rmtree(path=path, ignore_errors=False, onerror=handleRmtreeError)
  else:
  raise

Looking back to this code there is an infinite recursion bug if os.chmod fails 
for some reason in the os.listdir condition. I don't see an easy way to solve 
this...

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8442] Broken zipfile with python 3.2 on osx

[Alexander Belopolsky]

Alexander Belopolsky  added the comment:

I cannot reproduce this behavior on my MacBook running OSX 10.6.2.

$ ./python.exe Lib/test/test_distutils.py 
...
--
Ran 168 tests in 3.850s

OK (skipped=4)

Also, cp437 appears to be a valid encoding:

Python 3.2a0 (py3k:80615M, Apr 29 2010, 10:00:45) 
[GCC 4.2.1 (Apple Inc. build 5646) (dot 1)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> b"".decode('cp437')
''
>>> b"abcde".decode('cp437')
'abcde'

--
nosy: +Alexander.Belopolsky

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8523] shutil.rmtree and os.listdir cannot recover on error conditions

[Tarek Ziadé]

Tarek Ziadé  added the comment:

> Well, I don't think removing the current onerror support is a viable 
> option for backward compatibility reasons, 
> so we might as well fix it.  

The options could be deprecated since the new behavior would *return* errors.

> Do you have some use cases in mind, Tarek?

What I have in mind is robustness and simplicity: 

robustness because rmtree() will stop calling third party code that can 
possibly fail and blow the whole process, while working at removing the tree. 

Simplicity because, if it fails at removing some files using the usual os.* 
APIs, it will just return these errors.

Having this two phases-process will ensure that rmtree() did all that was 
possible to remove files.

And as I said previously, I am curious to know what is going to be done in the 
onerror() function when something fails in rmtree(). I doubt any third-party 
code will do better.

This statement "I couldn't copy this file, try it yourself" seems doomed to 
complexity.

If the only use case for onerror() is to silent failures, returning these 
failures seem quite enough. Ala smtp when you get back a list of mails that 
couldn't be send: it doesn't ask you to send them by yourself, just informs you.

Now maybe we do miss some APIs to check for a file tree sanity, like:

- are the permissions the same throughout the tree ?
- is there any link that will make rmtree() fail ? 
- etc/

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8442] Broken zipfile with python 3.2 on osx

[Ronald Oussoren]

Ronald Oussoren  added the comment:

There were some other build problems at the time, I haven't verified yet if the 
fixes for those problems also fixed this issue. I will do so over the weekend.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8523] shutil.rmtree and os.listdir cannot recover on error conditions

[Tarek Ziadé]

Tarek Ziadé  added the comment:

Looking at your example rubenlm, it appears like a case that is missing in 
rmtree().

You are trying to chmod your tree if a file in there cannot be removed because 
of the permissions. This sounds like something we need to add in rmtree() 
directly, for example under a "force_permissions" flag that would handle 
permission failures by trying to chmod.

I think rmtree() should not try to delegate the hard work to third party code, 
and should try to handle as much failures as possible, 
and just return errors.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8564] Update documentation on doctest/unittest2 integration

[Michael Foord]

Michael Foord  added the comment:

Looks like a good addition to the documentation to me.

--
nosy: +michael.foord

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8569] Upgrade OpenSSL in Windows builds

[Brian Curtin]

Brian Curtin  added the comment:

Tools/buildbot/external-common.bat does the checkout of OpenSSL 0.9.8l from 
svn.python.org/projects/external. What does it take to put a new 1.x version 
out there?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8552] msilib can't create large CAB files

[Bill Janssen]

Bill Janssen  added the comment:

Another bit of info.  It's the frequent commits that seem to fix the problem; 
when I comment those out of the __del__ method, it fails as before.  I also 
notice that the finished installer is about twice the size of the two data 
files in it (the CAB file and my zip file).  Seems like a lot of overhead.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8404] Set operations don't work for dictionary views

[Alexander Belopolsky]

Alexander Belopolsky  added the comment:

The patch looks fine.  I verified that the new tests pass on trunk and py3k.  I 
am attaching a patch for py3k with a forward port of set opereations and repr 
tests.

--
nosy: +Alexander.Belopolsky
Added file: http://bugs.python.org/file17127/issue8404_tests_py3k.diff

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8570] 2to3 crashes with "AttributeError: 'int' object has no attribute 'startswith'"

[rom16384]

New submission from rom16384 :

The attached file crashes 2to3 with traceback:

Traceback (most recent call last):
  File "/usr/bin/2to3", line 6, in 
sys.exit(main("lib2to3.fixes"))
  File "/usr/lib/python2.6/lib2to3/main.py", line 129, in main
rt.refactor(args, options.write, options.doctests_only)
  File "/usr/lib/python2.6/lib2to3/refactor.py", line 196, in refactor
self.refactor_file(dir_or_file, write, doctests_only)
  File "/usr/lib/python2.6/lib2to3/refactor.py", line 235, in refactor_file
tree = self.refactor_string(input, filename)
  File "/usr/lib/python2.6/lib2to3/refactor.py", line 260, in refactor_string
self.refactor_tree(tree, name)
  File "/usr/lib/python2.6/lib2to3/refactor.py", line 294, in refactor_tree
self.traverse_by(self.post_order_heads, tree.post_order())
  File "/usr/lib/python2.6/lib2to3/refactor.py", line 316, in traverse_by
results = fixer.match(node)
  File "/usr/lib/python2.6/lib2to3/fixes/fix_numliterals.py", line 18, in match
(node.value.startswith("0") or node.value[-1] in "Ll"))
AttributeError: 'int' object has no attribute 'startswith'


The code is from a version of pupynere, trimmed to reveal the traceback.
Python 2.6.4, OS: Ubuntu 9.10 (Karmic).

--
components: 2to3 (2.x to 3.0 conversion tool)
files: 2to3_crash.py
messages: 104518
nosy: rom16384
priority: normal
severity: normal
status: open
title: 2to3 crashes with "AttributeError: 'int' object has no attribute 
'startswith'"
type: crash
versions: Python 2.6
Added file: http://bugs.python.org/file17128/2to3_crash.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8413] String interpolation doesn't work with sys.version_info

[Alexander Belopolsky]

Alexander Belopolsky  added the comment:

I am not sure fixing this quirk of %-formatting is worth the trouble given that 
one simply use new style {}-formatting:

$ python-c 'import sys; print("{}.{}.{}-{}-{}".format(*sys.version_info))'
3.2.0-alpha-0

or a work-around

$ python -c 'import sys; print("%s.%s.%s-%s-%s" % tuple(sys.version_info))'
3.2.0-alpha-0

--
nosy: +Alexander.Belopolsky

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8535] passing optimization flags to the linker required for builds with gcc -flto

[Matthias Klose]

Matthias Klose  added the comment:

my understanding is that the builder is allowed to overwrite OPT, but not 
BASE_CFLAGS.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8413] String interpolation doesn't work with sys.version_info

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Well, the problem is that it's a regression from 2.6.
It also shows why these "fancy" structs aren't necessarily a good idea.
I agree fixing in py3k is less important, though it would be nice too.

--
nosy: +pitrou

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8571] zlib causes a SystemError when decompressing a chunk >1GB

[Denis Dmitriev]

New submission from Denis Dmitriev :

There's a bug in python's zlibmodule.c that makes it raise SystemError whenever 
it tries to decompress a chunk larger than 1GB is size. Here's an example of 
this in action:

dmitr...@...:~/moo/zlib_bug> cat zlib_bug.py 
import zlib

def test_zlib(size_mb):
print "testing zlib with a %dMB object" % size_mb
c = zlib.compressobj(1)
sm = c.compress(' ' * (size_mb*1024*1024)) + c.flush()
d = zlib.decompressobj()
dm = d.decompress(sm) + d.flush()

test_zlib(1024)
test_zlib(1025)

dmitr...@...:~/moo/zlib_bug> python2.6 zlib_bug.py 
testing zlib with a 1024MB object
testing zlib with a 1025MB object
Traceback (most recent call last):
  File "zlib_bug.py", line 11, in 
test_zlib(1025)
  File "zlib_bug.py", line 8, in test_zlib
dm = d.decompress(sm) + d.flush()
SystemError: Objects/stringobject.c:4271: bad argument to internal function

dmitr...@...:~/moo/zlib_bug>

A similar issue was reported in issue1372; however, either this one is 
different, or the issue still exists in all versions of Python 2.6 that I 
tested, on both Solaris and Mac OS X. These are all 64-bit builds and have no 
problem manipulating multi-GB structures, so it's not an out-of-memory 
condition:

dmitr...@...:~/moo/zlib_bug> python2.6   
Python 2.6.1 (r261:67515, Nov 18 2009, 12:21:47) 
[GCC 4.3.3] on sunos5
Type "help", "copyright", "credits" or "license" for more information.
>>> len(' ' * (6000*1024*1024))
6291456000
>>>

--
components: Library (Lib)
messages: 104522
nosy: ddmitriev
priority: normal
severity: normal
status: open
title: zlib causes a SystemError when decompressing a chunk >1GB
type: crash
versions: Python 2.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8413] String interpolation doesn't work with sys.version_info

[Eric Smith]

Eric Smith  added the comment:

The other thing to do would be to convince PyTuple_Check that PyStructSequences 
are tuples, but that would no doubt come with its own set of regressions.

Since this problem is 1) hard to fix and 2) probably of minimal impact, I think 
the best course is to do nothing.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8413] String interpolation doesn't work with sys.version_info

[Alexander Belopolsky]

Alexander Belopolsky  added the comment:

The recommended way to check that an object is an instance of a namedtuple  is 
to check for the _fields attribute.  See issue7796, msg99869.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8413] String interpolation doesn't work with sys.version_info

[Eric Smith]

Eric Smith  added the comment:

Yes, but sys.version_info isn't a namedtuple (which are in fact tuples), it's 
the (sort-of) C equivalent, which isn't a real tuple.

>>> from collections import namedtuple
>>> x = namedtuple('x', 'a b c')
>>> '%s %s %s' % x(1, 2, 3)
'1 2 3'

Hmm, but sys.version_info is a tuple:
>>> isinstance(sys.version_info, tuple)
True

I'll have to check if PyTuple_Check returns true or not. Maybe the problem is 
in the mapping check.

I'll investigate more.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8464] tarfile creates tarballs with execute permissions set

[Lars Gustäbel]

Lars Gustäbel  added the comment:

I applied the patch and added a test case (see r80616-r80619). Thanks for the 
report.

--
resolution:  -> accepted
stage:  -> committed/rejected
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8557] subprocess PATH semantics

[R. David Murray]

R. David Murray  added the comment:

Changing the default value of shell is not an option anyway.

The behavior you describe is exactly what one should expect: the environment in 
which the executable is located is the environment of the process calling 
Popen, not the environment passed to Popen.  The environment passed to Popen is 
the environment in which the subprocess executes.  When using shell=True, this 
is the environment in which the shell executes, and the *shell* then looks up 
the executable in that new environment.  As far as I know this behavior is the 
same on both Windows and Unix, and thus is not a portability issue.  (How the 
shell works can be a portability issue, though.)

I'm not sure that this needs to be documented explicitly, as it is a logical 
consequence of how subprocesses work, but if you want to suggest a doc update 
I'll take a look at it.

I suspect your Unix example is about the fragility of the rules for computing 
sys.executable (there's an issue in the tracker about that...you may get a 
different result on trunk), but I haven't checked it.

--
nosy: +r.david.murray
title: subprocess portability issue -> subprocess PATH semantics

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8563] [PEP 3147] compileall.compile_file() creates empty __pycache__ directories for non-.py files

[Barry A. Warsaw]

Barry A. Warsaw  added the comment:

Thanks for finding this bug.  I'm not sure about the second chunk of your diff 
(the one that removes __pycache__).  In the future, it would help to include a 
unittest case that illustrates the problem.  Here's a patch that includes a 
test for that specific problem, along with a narrowed down patch.  Can you 
explain why the other chunk is necessary (preferably with a unittest)?

--
Added file: http://bugs.python.org/file17129/8563.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8563] [PEP 3147] compileall.compile_file() creates empty __pycache__ directories for non-.py files

[Barry A. Warsaw]

Changes by Barry A. Warsaw :


--
assignee:  -> barry

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8413] String interpolation doesn't work with sys.version_info

[Raymond Hettinger]

Raymond Hettinger  added the comment:

IIRC, there is an open ticket to make structseq inherit from tuple to avoid 
just this kind of problem.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8413] String interpolation doesn't work with sys.version_info

[Eric Smith]

Eric Smith  added the comment:

Looks like that's issue 1820.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8413] String interpolation doesn't work with sys.version_info

[Alexander Belopolsky]

Alexander Belopolsky  added the comment:

On Thu, Apr 29, 2010 at 11:52 AM, Raymond Hettinger
 wrote:
..
> IIRC, there is an open ticket to make structseq inherit from tuple to avoid 
> just this kind of problem.
>

Indeed, see issue1820.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8572] httplib getheader() does not work as documented

[Walter Woods]

New submission from Walter Woods :

Calling HTTPResponse.getheader('Testabnew', 'Default') throws an exception 
rather than returning default, python 3.1.2.  Problem code appears to be line 
601 of client.py:


def getheader(self, name, default=None):
if self.headers is None:
raise ResponseNotReady()
-return ', '.join(self.headers.get_all(name, default))

Which should probably changed to:

+result = self.headers.get_all(name, None)
+if result:
+return ', '.join(result)
+else:
+return default

Not as elegant, but what appears to happen is if default is not an array, then 
get_all returns it, and the string join fails with a TypeError.

--
messages: 104532
nosy: Walter.Woods
priority: normal
severity: normal
status: open
title: httplib getheader() does not work as documented
type: crash
versions: Python 3.1

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8563] [PEP 3147] compileall.compile_file() creates empty __pycache__ directories for non-.py files

[Arfrever Frehtes Taifersar Arahesis]

Arfrever Frehtes Taifersar Arahesis  added the comment:

Here's an example, which shows that an empty __pycache__ has been created:

$ mkdir test
$ echo ":" > test/file.py
$ tree test
test
└── file.py

0 directories, 1 file
$ python3.2 -c 'import compileall; compileall.compile_file("test/file.py")'
Compiling test/file.py ...
***   File "test/file.py", line 1
:
^
SyntaxError: invalid syntax

$ tree test
test
├── file.py
└── __pycache__

1 directory, 1 file

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8572] httplib getheader() throws error instead of default

[Walter Woods]

Changes by Walter Woods :


--
title: httplib getheader() does not work as documented -> httplib getheader() 
throws error instead of default

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8560] regrtest: add a minimal "progress bar"

[R. David Murray]

R. David Murray  added the comment:

-1

IMO it just makes the output messier and less readable, and I personally am 
fine with judging the progress by the filenames.

--
nosy: +r.david.murray

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5559] IDLE Output Window 's goto fails when path has spaces

[R. David Murray]

R. David Murray  added the comment:

I think the issue is still open waiting for a unit test.  On the other hand, 
how likely is it that someone is going to write one at this point?  If someone 
doesn't speak up soon I think you can close it.

--
nosy: +r.david.murray

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8565] Always run regrtest.py with -bb

[R. David Murray]

R. David Murray  added the comment:

There are currently (at least) two places where regrtest is invoked by the 
buildbots, one for unix and one for windows.  The flags used are not always in 
sync, but probably should be.

I think it is probably better to not hack regrtest for this, since that would 
actually reduce its flexibility, but I'm open to argument on that. I'm going to 
set myself up an alias for running the tests:

   alias pytest="./python -E -tt -bb -Wd -3 -m test.regrtest"

That form for running regrtest should probably be added to the dev docs as a 
recommendation.

--
nosy: +r.david.murray

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8571] zlib causes a SystemError when decompressing a chunk >1GB

[Denis Dmitriev]

Denis Dmitriev  added the comment:

Alright, I think this is caused by the following:

static PyObject *
PyZlib_objdecompress(compobject *self, PyObject *args)
{
int err, inplen, old_length, length = DEFAULTALLOC;
int max_length = 0;

The problem is that inplen, length, old_length, and max_length are all ints, 
whereas they should be Py_ssize_t. I think replacing them should make the bug 
go away. (I can't test it right now though because I'm having trouble compiling 
zlibmodule on my current machine)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7079] file_close() ignores return value of close_the_file

[Daniel Stutzbach]

Changes by Daniel Stutzbach :


Removed file: http://bugs.python.org/file15076/fileobject.diff

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7079] file_close() ignores return value of close_the_file

[Daniel Stutzbach]

Changes by Daniel Stutzbach :


Removed file: http://bugs.python.org/file15077/crash.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8084] pep-0370 on osx duplicates existing functionality

[R. David Murray]

R. David Murray  added the comment:

Since you want it before the next beta, I'm promoting it to release blocker.  
Benjamin can reduce it if needed when we get down to the wire.

--
nosy: +r.david.murray
priority: high -> release blocker

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7079] file_close() ignores return value of close_the_file

[Daniel Stutzbach]

Changes by Daniel Stutzbach :


Added file: http://bugs.python.org/file17130/file_close_test.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7079] file_close() ignores return value of close_the_file

[Daniel Stutzbach]

Changes by Daniel Stutzbach :


Added file: http://bugs.python.org/file17131/file_close.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7079] file_close() ignores return value of close_the_file

[Daniel Stutzbach]

Daniel Stutzbach  added the comment:

I reworked my test script into a unit test.  Thanks for pointing me to 
test_file2k.py.  I leveraged the infrastructure that was already there.

I've also uploaded a new patch that uses tabs instead of spaces, to match the 
rest of fileobject.c.

--
stage: unit test needed -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8552] msilib can't create large CAB files

[Bill Janssen]

Bill Janssen  added the comment:

Ah, found the size problem -- I was measuring something in 512 blocks not 1KB 
blocks.  Never mind.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8570] 2to3 crashes with "AttributeError: 'int' object has no attribute 'startswith'"

[R. David Murray]

Changes by R. David Murray :


--
nosy: +benjamin.peterson
type: crash -> behavior
versions: +Python 2.7, Python 3.1, Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue808164] socket.close() doesn't play well with __del__

[Daniel Stutzbach]

Daniel Stutzbach  added the comment:

How do I write a unit test to check that socket.__del__ doesn't refer to any 
globals?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1820] Enhance Object/structseq.c to match namedtuple and tuple api

[Eric Smith]

Changes by Eric Smith :


--
nosy: +eric.smith

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2715] Remove carbon-specific code from binhex

[Terry J. Reedy]

Terry J. Reedy  added the comment:

I would close this, but I am not sure what the resolution should be.

--
nosy: +tjreedy
status: pending -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue770280] PyMarshal_ReadLastObjectFromFile

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Can this be closed as either out-of-date or rejected?

--
nosy: +tjreedy
status: pending -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3328] When PyObject_CallMethod fails, refcount is incorrect

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3536] case conversion problems in Turkish

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3957] [contextlib] Reverse order of locking

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4262] import and compile() do not treat trailing whitespace the same

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3433] Mac, 3.0 framework install error with fink cp

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4025] C99 comments in Python 2.6 break build on AIX 6.1

[Terry J. Reedy]

Terry J. Reedy  added the comment:

In the absence of further complaints, this appears to really be fixed. Should 
it be closed as such?

--
nosy: +tjreedy
status: pending -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue770280] PyMarshal_ReadLastObjectFromFile

[Mark Dickinson]

Mark Dickinson  added the comment:

I think this is superseded by issue 7332, which is now fixed in trunk (but not 
in 2.6).

--
nosy: +mark.dickinson, pitrou
resolution: remind -> out of date
status: open -> closed
superseder:  -> python script segment fault at PyMarshal_ReadLastObjectFromFile 
in import_submodule

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1178510] configure: refuses setgroups

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Closing this pending 2.4 Irix issue as out of date.
Martin, reopen if you object.

--
nosy: +tjreedy
resolution:  -> out of date
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5407] Broken Py3.1 release build in Visual Studio 2005

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5494] Failure in test_httpservers on Linux

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue785031] MacPython installer fails on UFS filesystem

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1004810] Carbon.File fails if server vol is mounted after launch

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2715] Remove carbon-specific code from binhex

[Mark Dickinson]

Mark Dickinson  added the comment:

Closing as fixed.

--
resolution:  -> fixed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2715] Remove carbon-specific code from binhex

[Mark Dickinson]

Changes by Mark Dickinson :


--
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1473979] test test_capi crashed -- thread.error: can't allocate lock

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue658693] cPickle does relative import

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2016] Crash when modifying the **kwargs passed to a function.

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Is everything fixed, so this can be closed?

--
nosy: +tjreedy
status: pending -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1367628] use PyOS_ReadlineFunctionPointer in non-interractive input

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1027] uudecoding (uu.py) does not supprt base64, patch attached

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8570] 2to3 crashes with "AttributeError: 'int' object has no attribute 'startswith'"

[Giampaolo Rodola']

Changes by Giampaolo Rodola' :


--
nosy: +giampaolo.rodola

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6788] codecs.open on Win32 does not force binary mode

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8569] Upgrade OpenSSL in Windows builds

[Giampaolo Rodola']

Changes by Giampaolo Rodola' :


--
nosy: +giampaolo.rodola

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6883] OptionParser.allow_interspersed_args is undocumented

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Skip, can we close this?

--
nosy: +tjreedy
status: pending -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com