[issue7998] MacPython 2.7a3 posix_spawn error for build using --with-framework-name

[Ronald Oussoren]

Ronald Oussoren  added the comment:

Fix in r78755 (2.7) and r78756 (3.2)


(the issue doesn't affect 2.6 or 3.1 because those have another implementation 
of the python/pythonw command)

--
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
versions: +Python 3.2

___
Python tracker 

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

[issue8067] OS X Installer: build errors on 10.6 when targeting 10.4 and earlier

[Ronald Oussoren]

Ronald Oussoren  added the comment:

Barry and Benjamin: IMHO this should be fixed before 2.6.5 and 3.1.2 are 
released, the patch is safe and works (and is already in the trunk).

--
nosy: +barry, benjamin.peterson
priority:  -> release blocker

___
Python tracker 

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

[issue8066] OS X installer: readline module breaks when targeting on 10.5 or 10.6

[Ronald Oussoren]

Ronald Oussoren  added the comment:

Barry: this definitely needs to be applied before 2.6.5 is released, without 
the patch I cannot build the mac installers.

The patch disables support for libedit when targetting 10.4, which is IMHO 
correct because as Ned notes libedit's readline emulation is totally broken in 
10.4.

--
priority:  -> release blocker

___
Python tracker 

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

[issue7995] On Mac / BSD sockets returned by accept inherit the parent's FD flags

[Ronald Oussoren]

Ronald Oussoren  added the comment:

I've removed 2.5 and added 3.2 because there won't be further bugfix releases 
of 2.5 and the issue also affects 3.2.

IMHO changing this behavior is not a bugfix and is therefore out of scope for 
2.6.x, in particular because this change might break code that runs fine on OSX 
and assumes the current behavior.

The documntation is not entirely clear on the behavior of the accept method, 
the best I could find is the documentation of the setblocking method: that says 
that all sockets are blocking by default, that would mean that the result of 
accept should be a blocking socket.

I'm therefore +1 for this change. I'm setting the 'needs review' flag because 
I'd like some input from other developers as well.

--
keywords: +needs review
versions: +Python 3.2 -Python 2.5

___
Python tracker 

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

[issue5262] PythonLauncher considered harmfull

[Ronald Oussoren]

Ronald Oussoren  added the comment:

I propose to at least change the code in pythonlauncher to warn if it is the 
default association for python files, that is to reverse the test that it 
currently does.

That way users can still set pythonlauncher as the launcher for a specific 
files, but would get a warning when they make pythonlauncher the default action 
for python files.

BTW. I still think that pythonlauncher is unsafe and should be removed.

--

___
Python tracker 

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

[issue8047] Serialiser in ElementTree returns unicode strings in Py3k

[Stefan Behnel]

Stefan Behnel  added the comment:

It has been brought up several times that ET is special in the stdlib in that 
it is an externally maintained package. Correct me if I'm wrong, but the rules 
seem to be: features come outside, adaptation to Py3 can happen inside. What we 
are talking about here is a new feature that makes sense for both Py2 and Py3. 
We are not talking about a bug fix, neither is this an adaptation to Py3. It is 
a new feature that was added inside of the standard library and that is not 
compatible with the external libraries that are supposed to implement the same 
interface, namely, ElementTree and lxml.etree.

--

___
Python tracker 

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

[issue8083] urllib proxy interface is too limited

[Ronald Oussoren]

New submission from Ronald Oussoren :

The proxy support code in urllib is imho too specific and cannot easily support 
dynamic proxy configuration using a proxy.pac file.

That is, the code assumes that there is at most one proxy per protocol, while 
this is not quite true in practice.  A proxy.pac can refer different URLs to 
different proxies (or exclude some from proxying).

This could be solved by adding a new proxy hook to urllib, something like:

def getproxies_for_url(url) -> [info, ...]

That is, the argument is the string for an URL, the result is a list of proxies 
that can be used to fetch the URL.

This hook would allow us to provide a hook on OSX that enables python scripts 
to use the system proxy settings, even when those are complex (such as by using 
proxy autoconfiguration).

--
components: Library (Lib)
messages: 100573
nosy: ronaldoussoren
severity: normal
stage: needs patch
status: open
title: urllib proxy interface is too limited
type: feature request
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

[issue8002] on OSX the file creation date not available in os.stat

[Ronald Oussoren]

Ronald Oussoren  added the comment:

I've done some research: the st_birthtime field is available when the python 
executable is build using MACOSX_DEPLOYMENT_TARGET=10.5 (or later), not for 
10.4.

Adding support for st_birthtime for MACOSX_DEPLOYMENT_TARGET=10.4 is possible 
but requires significant code duplication in posixmodule.c. 

IMO it adding this support is not worth the effort or the additional code 
complexity.

--

___
Python tracker 

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

[issue7072] isspace(0xa0) is true on Mac OS X

[Ronald Oussoren]

Ronald Oussoren  added the comment:

I've attached a patch that fixes the issue and enables all test_locale tests on 
OSX 10.6. 

(I will test if the tests can also be enabled on 10.5 when applying the patch).

--
keywords: +needs review, patch
resolution:  -> accepted
Added file: http://bugs.python.org/file16481/issue7072.patch

___
Python tracker 

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

[issue1530559] struct.pack raises TypeError where it used to convert

[Mark Dickinson]

Mark Dickinson  added the comment:

Here's a patch to restore the old usage of __int__ to convert non-integer 
arguments;  it also produces a DeprecationWarning whenever __int__ is used in 
this way.  For consistency and simplicity, __int__ will be tried for *any* 
non-integer argument when packing with an integer format;  this goes beyond the 
conversions that 2.6 allows. (In 2.6, the behaviour is somewhat random: it 
works only for 'bBhHil' in native mode and 'bhil' in non-native mode.)

It doesn't seem worth deliberately trying __long__ as well, so I've left that 
out.  So there's still some possibility for breakage relative to 2.6, when (1) 
packing using 'Q' or 'q', *and* (2) the object to be packed defines __long__ 
but not __int__, or defines both __long__ and __int__ in inconsistent ways.  
The likelihood of (2) seems small enough that this isn't worth worrying about 
in practice (and the workaround is easy, too).

Andreas, are you in a position to test this patch?

Supporting conversions to integer via __index__ is orthogonal to this;  I'll 
take a look at Meador's patch shortly.

--
Added file: http://bugs.python.org/file16482/issue1530559__int__.patch

___
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]

New submission from Ronald Oussoren :

The implementation of pep-0370 treats OSX like any other unix platform. 

This is problemantic for two reasons: first of all OSX already had a per-user 
directory before pep-0370 was implement: ~/Library/Python/X.Y, which means 
there are now two per-user directories on OSX. Secondly the pep-0370  per-user 
directory does not honor platform conventions.

I therefore propose to change pep-0370 behavior on OSX: 
* remove ~/.local as the user-base
* upgrade ~/Library/Python/X.Y to a pep-0370 compatible directory
  (that is: introduce the additional subdirectories that are used
   in pep-0370)
* upgrade /Library/Python/X.Y to the same structure

--
assignee: ronaldoussoren
components: Installation, Library (Lib), Macintosh
keywords: needs review
messages: 100577
nosy: ronaldoussoren
severity: normal
status: open
title: pep-0370 on osx duplicates existing functionality
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

[issue8084] pep-0370 on osx duplicates existing functionality

[Ronald Oussoren]

Ronald Oussoren  added the comment:

The attached patch is untested an implements the proposed behavior for 
framework builds, unix builds would keep the unix-style behavior (and would 
lose access to ~/Library/Python).

The patch is slightly complicated by adding support for --with-framework-name 
as well, but that shouldn't make the patch harder to read.

BTW. The "needs review" part is more for the proposed change in behavior that 
for the actual patch, I'm confident that I can create a correct patch but I'm 
not sure if the change is behavior is uncontroversial.

--
keywords: +patch
Added file: http://bugs.python.org/file16483/issue8084.patch

___
Python tracker 

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

[issue8002] on OSX the file creation date not available in os.stat

[Floris van Manen]

Floris van Manen  added the comment:

On Mar 7, 2010, at 13:08, Ronald Oussoren wrote:

> IMO it adding this support is not worth the effort or the additional code 
> complexity.

I do agree.
We have to look forwards ...

F

--

___
Python tracker 

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

[issue8085] PyObject_GC_VarNew should be PyObject_GC_NewVar

[Florian Weimer]

New submission from Florian Weimer :

The manual mentions the wrong C function (Var and New are transposed).

--
assignee: georg.brandl
components: Documentation
messages: 100580
nosy: fw, georg.brandl
severity: normal
status: open
title: PyObject_GC_VarNew should be PyObject_GC_NewVar
versions: Python 2.6, Python 3.1

___
Python tracker 

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

[issue1530559] struct.pack raises TypeError where it used to convert

[Mark Dickinson]

Mark Dickinson  added the comment:

Updated patch, with slightly saner warnings checks.

--
Added file: http://bugs.python.org/file16484/issue1530559__int__2.patch

___
Python tracker 

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

[issue8047] Serialiser in ElementTree returns unicode strings in Py3k

[Antoine Pitrou]

Antoine Pitrou  added the comment:

As Florent said, it is a rule of py3k to avoid implicit encoding/decoding. The 
fact that it could have made sense for 2.x as well is not relevant, since the 
change was only done in py3k (and for good reason: we normally try not to break 
compatibility without prior notice).

In any case, I have trouble understanding your concern here. Do you think the 
change is bad? Is it really that difficult to support it in lxml?

--

___
Python tracker 

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

[issue5341] A selection of spelling errors and typos throughout source

[R. David Murray]

R. David Murray  added the comment:

Georg can correct me if I'm wrong, but I believe we generally only rewrap lines 
when we change the text for some other reason.  My observation was that Georg 
re-wraps doc text to 79 chars, so that's what I've been doing.  PEP 8 really 
only applies to source files, the docs are (at least currently) Georg's demesne.

--
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

[issue5341] A selection of spelling errors and typos throughout source

[Georg Brandl]

Georg Brandl  added the comment:

David is correct, rewrapping while editing is intrusive enough.

The docs should be wrapped at 79/80 characters.  The reason that most files 
have longer lines is that the latex to rest converter tool had a flaw in the 
wrapping code that I didn't notice until after the conversion.

Applied the two other patches in r78760.

--

___
Python tracker 

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

[issue5341] A selection of spelling errors and typos throughout source

[Éric Araujo]

Éric Araujo  added the comment:

> rewrap lines when we change the text for some other reason.
Doesn’t that make harder to review the real changes when they are mixed 
with rewrapping?

 > PEP 8 really only applies to source files, the docs are (at least
 > currently) Georg's demesne.
(domain?) I was only citing PEP 8 as a reference, since there are some 
indications about line length of text paragraphs.

Cheers

--

___
Python tracker 

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

[issue5341] A selection of spelling errors and typos throughout source

[Georg Brandl]

Georg Brandl  added the comment:

> > rewrap lines when we change the text for some other reason.
> Doesn’t that make harder to review the real changes when they are mixed 
> with rewrapping?

That's true. I wouldn't do it in patches I mean someone else to review. But 
many times it's the other way round: I apply doc changes from some patch, and 
then rewrap before committing.

--

___
Python tracker 

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

[issue5341] A selection of spelling errors and typos throughout source

[R. David Murray]

R. David Murray  added the comment:

No, I meant demense (I even looked up the spelling).  The word is related to 
domain, but has a somewhat more precise shading of meaning :)

 A lord's chief manor place, with that part of the lands
 belonging thereto which has not been granted out in tenancy;
 a house, and the land adjoining, kept for the proprietor's
 own use. [Written also {demain}.] --Wharton's Law Dict.

In other words, Georg is lord of this particular manor, unless he assigns a 
piece to someone else...it seemed in keeping with the Python tradition of 
having a BDFL.

--

___
Python tracker 

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

[issue5341] A selection of spelling errors and typos throughout source

[Éric Araujo]

Éric Araujo  added the comment:

Thanks for the new word. (I checked with my local dictd but not on the 
Intertubes, should have).

Having designated active maintainers for modules and areas is indeed great.

Cheers

--

___
Python tracker 

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

[issue8067] OS X Installer: build errors on 10.6 when targeting 10.4 and earlier

[Benjamin Peterson]

Benjamin Peterson  added the comment:

2010/3/7 Ronald Oussoren :
>
> Ronald Oussoren  added the comment:
>
> Barry and Benjamin: IMHO this should be fixed before 2.6.5 and 3.1.2 are 
> released, the patch is safe and works (and is already in the trunk).

Ok. Would you mind merging it?

--

___
Python tracker 

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

[issue1530559] struct.pack raises TypeError where it used to convert

[Mark Dickinson]

Mark Dickinson  added the comment:

Restored use of __int__ for all integer conversion codes in r78762.

--

___
Python tracker 

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

[issue1530559] struct.pack raises TypeError where it used to convert

[Mark Dickinson]

Mark Dickinson  added the comment:

Recent checkins messed up Meador Inge's __index__ patch;  here's a regenerated 
version.

--
Added file: http://bugs.python.org/file16485/issue-1530559__index__.patch

___
Python tracker 

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

[issue7143] get_payload(decode=True) eats last newline in base64 encoded payload

[R. David Murray]

R. David Murray  added the comment:

Your patch looks good, thank you.

I just realized that Barry isn't nosy on this issue.  I've checked, and the 
code in question dates back to email version 1.0...code of that long standing 
that exists specifically to implement the behavior we propose to change makes 
me wonder what we will break if we fix it.  Yet the current behavior seems 
clearly contrary to the RFCs to me.

Barry?  Any memory of why _bdecode exists and what will break if we fix it?

In any case I suspect that backporting this fix might be a bad idea, since 
existing code may be compensating for the current behavior and break if the 
behavior is fixed.

--
nosy: +barry
versions:  -Python 2.5, Python 2.6, Python 3.1

___
Python tracker 

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

[issue7173] Cython compiler run crashes CPython 3.1.1 and 3.2

[Benjamin Peterson]

Benjamin Peterson  added the comment:

Fixed in r78766.

--
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

[issue1530559] struct.pack raises TypeError where it used to convert

[Mark Dickinson]

Mark Dickinson  added the comment:

Comments and thoughts on the __index__ patch:

(1) Thank you for a remarkably complete patch!

(2) For 2.x, I'm a bit uncomfortable with introducing the extra Python layer on 
top of the C layer.  Partly I'm worried about accidentally breaking something 
(it's not 100% clear to me whether there might be hidden side-effects to such a 
change), but I also notice that this seems to have a significant impact on 
performance.  In fact, I seem to recall that the previously existing Python 
component of the struct module was absorbed into Modules/_struct.c precisely 
for performance reasons.

A quick, unscientific benchmark:  the time taken to run test_struct with this 
patch (excluding the changes to test_struct itself) on my machine (OS X 10.6, 
64-bit non-framework non-debug build of Python) is around 1.52--1.53 seconds;  
without the patch it's around 1.02--1.03 seconds.

(3) For 3.x, and for the issue 3132 work, I agree it might make sense to have a 
fatter Python layer;  this would also help other Python implementations that 
are trying to keep up with CPython.  I'm still a bit worried about performance, 
though.

(4) For 2.x, perhaps we don't need the extra __index__ functionality anyway, 
now that the previous use of __int__ has been restored.  That would give us a 
bit more time to think about this for 3.x.

--

___
Python tracker 

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

[issue8086] ssl.get_server_certificate new line missing

[Chris]

New submission from Chris :

I'm using ssl.get_server_certificate function. It returns a pem string. For 
each server I try, I get the string, but it is missing a newline "\n" before 
the -END CERTIFICATE- text. Any subsequent use of the string makes 
openssl throw up with a "bad end line" error.

ssl.PEM_cert_to_DER_cert can be used, and, subsequently the der string can be 
used elsewhere.

Example:
>>> fncert = ssl.get_server_certificate(("freenode.net", 443), 3)
>>> fncert
'-BEGIN 
CERTIFICATE-\nMIICFTCCAX6gAwIBAgIBAjANBgkqhkiG9w0BAQUFADBVMRswGQYDVQQKExJBcGFj\naGUgSFRUUCBTZXJ2ZXIxIjAgBgNVBAsTGUZvciB0ZXN0aW5nIHB1cnBvc2VzIG9u\nbHkxEjAQBgNVBAMTCWxvY2FsaG9zdDAeFw0wNzA1MDkxODM2MjVaFw0wODA1MDgx\nODM2MjVaMEwxGzAZBgNVBAoTEkFwYWNoZSBIVFRQIFNlcnZlcjEZMBcGA1UECxMQ\nVGVzdCBDZXJ0aWZpY2F0ZTESMBAGA1UEAxMJbG9jYWxob3N0MIGfMA0GCSqGSIb3\nDQEBAQUAA4GNADCBiQKBgQDYqJO6X9uwU0AyJ6H1WgYCZOqpZvdI96/LaDumT4Tl\nD6QvmXzAbM4okSHU3FEuSqR/tNv+eT5IZJKHVsXh0CiDduIYkLdqkLhEAbixjX/1\nfdCtGL4X0l42LqhK4TMFT5AxxsP1qFDXDvzl/yjxo9juVuZhCeqFr1YDKBffCIAn\ncwIDAQABMA0GCSqGSIb3DQEBBQUAA4GBAG0zi/KyzHxSsLHfrwTFh9330TaGj/3H\nuvhmBUPC3FOxbIH2y5CG/Ddg46756cfaxKKiqJV3I4dAgatQybE65ELc3wOWgs4v\n4VDGsFKbkmBLuCgnFaY+p4xvr2XL+bJmpm8+IQqW5Ob/OUSl7Vj4btHhF6VK29CI\n+DexDLRI0KqZ-END
 CERTIFICATE-\n'

Notice no "\n" before -END CERTIFICATE-\n

Platform: 
Linux x64
python 2.6.4

--
messages: 100595
nosy: offero
severity: normal
status: open
title: ssl.get_server_certificate new line missing
type: behavior
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

[issue7143] get_payload(decode=True) eats last newline in base64 encoded payload

[Joaquin Cuenca Abela]

Joaquin Cuenca Abela  added the comment:

Unfortunately the only way that I can see to reliably work around this is to 
bypass entirely get_payload, in this case fixing this bug will not affect 
people that do that negatively.

Some people may have more control over their attachments and they are 
unconditionally adding a \n to certain type of attachments. In this case they 
will get an extra \n after this patch.

If they are doing this, they certainly realized there was a bug, because this 
is only necessary for base64 encoded attachments and not for any other 
encoding. In this case I guess it's reasonable to expect that this bug will be 
fixed one day.

But you're right that the change is risky, an that we (at least I) are not sure 
why the code is the way it is.

Cheers,

--

___
Python tracker 

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

[issue8086] ssl.get_server_certificate new line missing

[Chris]

Chris  added the comment:

Did some more research and found this as the culprit:

in Lib/ssl.py

#
...
def get_server_certificate(addr, ssl_version=PROTOCOL_SSLv3, ca_certs=None):
...
return DER_cert_to_PEM_cert(dercert)

def DER_cert_to_PEM_cert(der_cert_bytes):

"""Takes a certificate in binary DER format and returns the
PEM version of it as a string."""

if hasattr(base64, 'standard_b64encode'):
# preferred because older API gets line-length wrong
f = base64.standard_b64encode(der_cert_bytes)
return (PEM_HEADER + '\n' +
textwrap.fill(f, 64) +
PEM_FOOTER + '\n')
else:
return (PEM_HEADER + '\n' +
base64.encodestring(der_cert_bytes) +
PEM_FOOTER + '\n')



Notice no '\n' before the PEM_FOOTER

--

___
Python tracker 

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

[issue7162] 2to3 does not convert __builtins__.file

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc  added the comment:

Unfortunately this patch would also replace legitimate uses of a "file" 
function.

--
assignee:  -> benjamin.peterson
nosy: +amaury.forgeotdarc, benjamin.peterson
stage:  -> patch review

___
Python tracker 

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

[issue8086] ssl.get_server_certificate new line missing

[R. David Murray]

R. David Murray  added the comment:

I think that's because encodestring tacks a 'courtesy newline' on to the end of 
the output it returns.  textwrap.fill does't, and I'm guessing that's the code 
path that your installation is taking.

--
components: +Library (Lib)
keywords: +easy
nosy: +r.david.murray
priority:  -> normal
stage:  -> test needed

___
Python tracker 

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

[issue8086] ssl.get_server_certificate new line missing

[R. David Murray]

Changes by R. David Murray :


--
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

[issue8086] ssl.get_server_certificate new line missing

[R. David Murray]

Changes by R. David Murray :


--
nosy: +janssen

___
Python tracker 

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

[issue8087] Unupdated source file in traceback

[Diego Mascialino]

New submission from Diego Mascialino :

Example:

 mod.py 
def f():
a,b,c = 1,2
print b


If i do:

>>> import mod
>>> mod.f()

I get:

Traceback (most recent call last):
  File "", line 1, in 
  File "mod.py", line 2, in f
a,b,c = 1,2
ValueError: need more than 2 values to unpack


If i fix the source:

 mod.py 
def f():
a,b,c = 1,2,3
print b


And do:

>>> mod.f()

I get:

Traceback (most recent call last):
  File "", line 1, in 
  File "mod.py", line 2, in f
a,b,c = 1,2,3
ValueError: need more than 2 values to unpack

The problem is that the source shown is updated, but the executed code is old, 
because it wasn't reloaded.

Feature request:

If the source code shown was modified after import time and it wasn't reloaded, 
a warning message should be shown.

Example:

Traceback (most recent call last):
  File "", line 1, in 
  File "mod.py", line 2, in f  WARNING: Modified after import!
a,b,c = 1,2,3
ValueError: need more than 2 values to unpack

or something like that. Maybe "use reload()" might appear.

--
components: Interpreter Core
messages: 100600
nosy: dmascialino, jjconti
severity: normal
status: open
title: Unupdated source file in traceback
type: feature request
versions: Python 2.7

___
Python tracker 

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

[issue8085] PyObject_GC_VarNew should be PyObject_GC_NewVar

[Luciano Bello]

Luciano Bello  added the comment:

patch added

--
keywords: +patch
nosy: +Luciano.Bello
Added file: http://bugs.python.org/file16486/PyObject_GC_VarNew_type.patch

___
Python tracker 

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

[issue8085] PyObject_GC_VarNew should be PyObject_GC_NewVar

[Luciano Bello]

Changes by Luciano Bello :


--
nosy: +jjconti

___
Python tracker 

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

[issue8059] @unittest.skip on a test method should prevent setUp from running

[Michael Foord]

Michael Foord  added the comment:

Fixed revision 78770.

--
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

[issue7998] MacPython 2.7a3 posix_spawn error for build using --with-framework-name

[Tom Loredo]

Tom Loredo  added the comment:

> Ronald Oussoren  added the comment:
> 
> Fix in r78755 (2.7) and r78756 (3.2)

Thanks for your attention to this, Ronald---and all the hard
work on the OS X support.

-Tom

-
This mail sent through IMP: http://horde.org/imp/

--

___
Python tracker 

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

[issue7670] _sqlite3: Block *all* operations on a closed Connection object

[Barry A. Warsaw]

Barry A. Warsaw  added the comment:

I'm going to let this one stay for 2.6.5 since we need another rc anyway.  
Thanks for the fix!

--
status: open -> closed

___
Python tracker 

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

[issue8067] OS X Installer: build errors on 10.6 when targeting 10.4 and earlier

[Barry A. Warsaw]

Barry A. Warsaw  added the comment:

Ned, thanks for the fix.  Ronald, please apply it to release26-maint for 2.6.5 
rc 2.

--
resolution:  -> accepted

___
Python tracker 

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

[issue8066] OS X installer: readline module breaks when targeting on 10.5 or 10.6

[Barry A. Warsaw]

Barry A. Warsaw  added the comment:

Ned, thanks again for another great OS X fix.  Ronald, please apply this to 
release26-maint for 2.6.5 rc 2.

--
resolution:  -> accepted

___
Python tracker 

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

[issue8082] Misleading exception when raising an object

[Barry A. Warsaw]

Barry A. Warsaw  added the comment:

Minor nit: it's questionable whether this should have gone in between 2.6.5 rc1 
and rc2.  It doesn't seem like a critical fix.  OTOH, it also seems harmless 
enough so I'm gonna let it slide.

--
nosy: +barry

___
Python tracker 

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

[issue8087] Unupdated source file in traceback

[Martin v . Löwis]

Martin v. Löwis  added the comment:

Displaying a warning whenever the code has changed on disk is clearly 
unacceptable - it is both expensive to check (and also, how frequent would you 
check?), and it would be annoying if you have long-running Python applications 
so this would just clutter the log files.

-1 on this request; users should just learn this aspect of Python. Also, it is 
not possible to get this perfect for many reasons, e.g. when you change a 
class, it will be impossible to update the code of existing instances even with 
reload.

--
nosy: +loewis

___
Python tracker 

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

[issue8085] PyObject_GC_VarNew should be PyObject_GC_NewVar

[Georg Brandl]

Georg Brandl  added the comment:

Thanks, applied in r78771.

--
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

[issue7449] A number tests "crash" if python is compiled --without-threads

[STINNER Victor]

STINNER Victor  added the comment:

Ok, here is my patch "version 4", based on jerry's nothreads_3.patch. Changes 
between version 3 and 4:

 - test_support: threading_setup() returns (1,) instead of None; reap_threads()
   simply returns the function instead of a dummy decorator
 - regrtest.py: display an error if -j/--multiprocess option is used
 - ctypes/test/test_errno.py, test_smtplib, test_socket, test_asynchat: skip
   some tests, not the whole file
 - test_logging, test_xmlrpc, test_file2k: move decorator from setUp() method
   to the class
 - test_capi: test threading variable value instead of the presence of the
   _test_thread_state function
 - test_capi, test_contextlib: move the decorator from methods to the class
 - test_multiprocessing: import threading (without try/except) after
   _multiprocessing because _multiprocessing depends on threading and so it
   will fail

All tests pass on both builds: with and without threads.

I'm not sure that my changes moving decorators from the setUp() method or other 
methods to the class is the right thing to do.

FYI tests skipped because of the missing thread module are listed in "xx skips 
unexped on linux2: ...". I don't think that it's a problem. We discuss about 
that on IRC and bitdancer suggested to leave regrtest.py unchanged:

"bitdancer> You should *definitely* not disable the skip message just because 
the threading module is missing, that would defeat the whole purpose of the 
message."

--
Added file: http://bugs.python.org/file16487/nothreads_4.patch

___
Python tracker 

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

[issue8039] precedence rules for ternary operator

[Georg Brandl]

Georg Brandl  added the comment:

if-else actually was already documented, under "boolean expressions".  It was 
merely missing from the precendence table.

I've now given it its own section, to make it stand out a bit better.  See 
r78772.

--
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

[issue7162] 2to3 does not convert __builtins__.file

[Ryan Coyner]

Ryan Coyner  added the comment:

I thought the whole point was that file[1] was removed in 3.0[2]? Or, are you 
saying that if somebody overloaded file with def file(...)? If that is the case 
would it be reasonable to check like this?

>>> file in list(__builtins__.__dict__.values())
True
>>> def file():
... pass
... 
>>> file in list(__builtins__.__dict__.values())
False
>>> 


[1] - http://docs.python.org/library/functions.html?highlight=file#file
[2] - http://docs.python.org/3.1/whatsnew/3.0.html#builtins

--

___
Python tracker 

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

[issue8044] Py_EnterRecursiveCall and Py_LeaveRecursiveCall are undocumented

[Georg Brandl]

Georg Brandl  added the comment:

Thanks! I've added documentation in r78773.

--
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

[issue7300] Unicode arguments in str.format()

[STINNER Victor]

Changes by STINNER Victor :


--
nosy: +haypo

___
Python tracker 

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

[issue7143] get_payload(decode=True) eats last newline in base64 encoded payload

[Barry A. Warsaw]

Barry A. Warsaw  added the comment:

Thanks for adding me to the nosy list.  Yep, this code is pretty old so it 
doesn't surprise me that its implementation isn't quite right.  Of course, I 
hate get_payload(decode=True) anyway and hope that goes away in email 6.

Having said that, I don't think this can be changed in Python 2.6.  It's pretty 
common for people to have workarounds for the devil they know and I'd bet that 
changing this behavior in 2.6.x would break people's code.  I'm okay for doing 
the sensible thing in Python 2.7 (though we should probably bump the email 
package's micro version).

--

___
Python tracker 

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

[issue8082] Misleading exception when raising an object

[Benjamin Peterson]

Benjamin Peterson  added the comment:

2010/3/7 Barry A. Warsaw :
>
> Barry A. Warsaw  added the comment:
>
> Minor nit: it's questionable whether this should have gone in between 2.6.5 
> rc1 and rc2.  It doesn't seem like a critical fix.  OTOH, it also seems 
> harmless enough so I'm gonna let it slide.

Thank you. My apologies for forgetting the state of that tree.

--

___
Python tracker 

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

[issue8038] Not all the new assert* unittest.TestCase methods have negative (not) equivalents

[Ryszard Szopa]

Ryszard Szopa  added the comment:

Hi,

I am the original reporter of the bug. Please forgive me if this is not the 
place for discussing the issue. 

I've thought about it, and stuff like assertDictNotEqual or 
assertSequenceNotEqual aren't really necessary - it is much easier (and 
shorter) to use assertNotEqual, and there's no need for any special formatting 
needed to say that something is equal when it shouldn't.

This is not the case for assertNotRegexpMatches, though. 
assertNot(re.match(...)) tells me only that False is not True. I'd like it to 
say *how* the text matches the regex (the matching part that is). (Sorry for 
repeating myself, I try to be clearer this time.)

So, this issue could be renamed to "Implement assertNotRegexpMatches."

--
nosy: +Ryszard.Szopa

___
Python tracker 

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

[issue8038] Provide unittest.TestCase.assertNotRegexpMatches

[Michael Foord]

Changes by Michael Foord :


--
title: Not all the new assert* unittest.TestCase methods have negative (not) 
equivalents -> Provide unittest.TestCase.assertNotRegexpMatches

___
Python tracker 

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

[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup

[STINNER Victor]

STINNER Victor  added the comment:

I think initsite() should be atomic: if any kind of error occurs, Python should 
print it and exit directly (exit code 1 to notice the error). If initsite() 
fails, Python is not complelty initialized.

site is responsible to initialiaze a lot of things:

 - Set all module' __file__ attribute to an absolute path
 - Remove duplicate entries from sys.path along with making them absolute
 - Add a per user site-package to sys.path
 - Add site-packages (and possibly site-python) to sys.path
 - Define new built-ins 'quit' and 'exit'.
 - Set 'copyright' and 'credits' in __builtin__"
 - Create builtin help() function
 - On Windows, some default encodings are not provided by Python, while they 
are always available as "mbcs" in each locale. Make them usable by aliasing to 
"mbcs" in such a case.
 - import sitecustomize
 - import usercustomize
 - del sys.setdefaultencoding
 - etc.

Be able to ignore the site initializations might be a security vulnerability.

Attached patch consider any exception as fatal: display the error and exit. I 
moved the call to _PyGILState_Init() before initsite() to avoid a crash in 
Py_Finalize() => see #8063.

--
keywords: +patch
nosy: +haypo
Added file: http://bugs.python.org/file16488/initsite.patch

___
Python tracker 

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

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

[STINNER Victor]

STINNER Victor  added the comment:

See also #3137.

--

___
Python tracker 

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

[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup

[STINNER Victor]

STINNER Victor  added the comment:

Using "valgrind --log-file=/tmp/trace ./python" to slow down Python, I found 
another bug in the interactive interpreter: if you press CTRL+c just after the 
initialization of the site module the exception will be ignored.

When a signal is catched, it's stored in a table, and the real handler is 
called later (by Py_MakePendingCalls()). Py_AddPendingCall() is called to 
ensure that the signal will be handled before the next Python instruction. In 
my case, the next Python instruction is "decode the string written by the user 
using the terminal encoding" called by the tokenizer... but the tokenizer 
ignores all errors (not only unicode errors): see tok_stdin_decode().

Recipe to catch the code responsible to ignore the keyboard interrupt exception 
(using gdb):
-
$ gdb ./python
(gdb) b initsite
Breakpoint 1, initsite ()
(gdb) run
...
Breakpoint 1, initsite ()
(gdb) next

(gdb) b signal_default_int_handler
Breakpoint 2
(gdb) signal SIGINT
Breakpoint 2, signal_default_int_handler
(gdb) b PyErr_Clear
Breakpoint 3
(gdb) cont
...
Breakpoint 3, PyErr_Clear ()
(gdb) where

-

Attached patch calls Py_MakePendingCalls() before PyRun_AnyFileExFlags() to 
avoid the tokenizer bug. It's just a workaround, not a real bugfix.

--
Added file: http://bugs.python.org/file16489/main_pending_calls.patch

___
Python tracker 

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

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc  added the comment:

I would keep the call to PyThreadState_Swap() next to PyThreadState_New(): 
create the thread state and install it. _PyGILState_Init() may come after.

--
nosy: +amaury.forgeotdarc

___
Python tracker 

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

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

[STINNER Victor]

Changes by STINNER Victor :


--

___
Python tracker 

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

[issue7449] A number tests "crash" if python is compiled --without-threads

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc  added the comment:

Did someone notice that on Windows, subprocess imports threading, and use 
threads for the communicate() method?

--
nosy: +amaury.forgeotdarc

___
Python tracker 

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

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc  added the comment:

haypo, it seems you removed the initial message...

--

___
Python tracker 

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

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

[STINNER Victor]

STINNER Victor  added the comment:

> haypo, it seems you removed the initial message...

I know... My mouse clicked on [remove] button, it wasn't me! I don't know how 
to restore it. The message: msg100432.

--

___
Python tracker 

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

[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()

[STINNER Victor]

STINNER Victor  added the comment:

I found the following issue in Roundup tracker to restore a deleted message:
http://psf.upfronthosting.co.za/roundup/meta/issue267

I tried to write the URL, but it doesn't work:
http://bugs.python.org/issue80...@action=edit&@a...@messages=100432

I tried also using Poster Firefox extension (to post a POST request, not a GET 
request), but it doesn't work. My URL should be wrong :-/

--

___
Python tracker 

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

[issue7449] A number tests "crash" if python is compiled --without-threads

[STINNER Victor]

STINNER Victor  added the comment:

> Did someone notice that on Windows, subprocess imports threading, 
> and use threads for the communicate() method?

No, I didn't ran the tests on Windows. I can expect that someone build Python 
on Linux without threads, but is Python used in embedded systems with Windows 
but without threads?

Since the patch is already huge, I would suggest to open a new issue (fix tests 
for Windows without threads).

--

___
Python tracker 

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

[issue7300] Unicode arguments in str.format()

[Pablo Mouzo]

Changes by Pablo Mouzo :


--
nosy: +pablomouzo

___
Python tracker 

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

[issue7143] get_payload(decode=True) eats last newline in base64 encoded payload

[R. David Murray]

R. David Murray  added the comment:

OK, patch (with comment tweaks to refer to this issue), and email minor version 
bump, applied to trunk in r78778.  It turns out that bdecode was already 
deleted in email 5 in py3k.  I did port the test in r78780.

Thanks Joaquin Cuenca Abela, and you now have the interesting distinction of 
being the first name listed in Misc/ACKS (because we've been maintaining it in 
sorted order by last name)

--
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed
versions:  -Python 3.2

___
Python tracker 

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

[issue7162] 2to3 does not convert __builtins__.file

[Joe Amenta]

Joe Amenta  added the comment:

Yes, the idea was that it doesn't seem outlandish for someone to do:
def file(something):
do_stuff()

You can use lib2to3.fixer_util.is_probably_builtin for this... modified the 
patch and attached.

--
Added file: http://bugs.python.org/file16490/issue7162-3.patch

___
Python tracker 

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

[issue8087] Unupdated source file in traceback

[Diego Mascialino]

Diego Mascialino  added the comment:

Martin, I am not talking about a loop checking source file changes.

I think the check could be done only when the traceback is printed.

The function PyErr_Display() calls PyTracBack_Print() and so on until 
_Py_DisplaySourceLine() is called. The latter reads the source file and prints 
the line. I don't know which is the best way to know if the source file was 
updated. But i think that it's possible to check it there.

I think this could apply only when using the interactive console.

--

___
Python tracker 

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

[issue8067] OS X Installer: build errors on 10.6 when targeting 10.4 and earlier

[Ronald Oussoren]

Ronald Oussoren  added the comment:

Committed in r78781 (2.6), r78782 (3.2) and r78783 (3.1)

--
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

[issue8066] OS X installer: readline module breaks when targeting on 10.5 or 10.6

[Ronald Oussoren]

Ronald Oussoren  added the comment:

Committed in r78784 (trunk), r78785 (2.6) and r78786 (3.2)

(BTW. I applied the patch to the trunk then used svnmerge to merge the patch 
into the other branches)

--
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