[issue3820] Python 3.0b3 doesn't start on German Win XP SP3/SP2

[Tim Pietzcker]

Tim Pietzcker <[EMAIL PROTECTED]> added the comment:

Thanks a lot, now it works! The download link is 

http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf

in case someone else needs it.

Best regards,
Tim

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3807] _multiprocessing build fails when configure --without-threads

[Hirokazu Yamamoto]

Changes by Hirokazu Yamamoto <[EMAIL PROTECTED]>:


--
keywords: +needs review
versions: +Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3811] Update Unicode database to 5.1.0

[Fredrik Lundh]

Fredrik Lundh <[EMAIL PROTECTED]> added the comment:

The patch looks fine to me (assuming that I didn't miss something 
critical hidden among the large table diffs).

(I'd probably named the "NODELTA" flag after what it is rather than what 
it isn't, but I cannot think of a short replacement right now, so let's 
leave it as it is.)

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3766] socket.socket.recv broken (unbearably slow)

[Thorben Krueger]

Thorben Krueger <[EMAIL PROTECTED]> added the comment:

As promised, here is the profiler output for a Mac (thanks Stefan). The
problem does NOT occur here, which should help greatly in tracking down
the cause in the socket library. Anyone into this?

$ python runme.py
500 packets @ 2 tokens each (500 very short lists)
0.0814669132233
14508 function calls in 0.082 CPU seconds

  Ordered by: internal time

  ncalls  tottime  percall  cumtime  percall filename:lineno(function)
15000.0480.0000.0480.000 {method 'recv' of
'_socket.socket' objects}
15000.0150.0000.0150.000 :1(sendall)
15000.0030.0000.0210.000 Client.py:8(send_int)
15000.0030.0000.0530.000 Client.py:16(read_int)
 5000.0030.0000.0570.000 Client.py:19(read_int_list)
15000.0020.0000.0020.000 struct.py:77(unpack)
15000.0020.0000.0020.000 struct.py:54(pack)
 5000.0010.0000.0220.000 Client.py:11(send_int_list)
   10.0010.0010.0820.082 runme.py:12(bench)
10000.0010.0000.0010.000 {method 'insert' of 'list'
objects}
10010.0010.0000.0010.000 {range}
 5000.0010.0000.0800.000 Client.py:28(spam)
15000.0000.0000.0000.000 {method 'unpack' of
'Struct' objects}
 5010.0000.0000.0000.000 {len}


1 packet @ 5 tokens (1 very long list)
5.20953297615
400018 function calls in 5.210 CPU seconds

  Ordered by: internal time

  ncalls  tottime  percall  cumtime  percall filename:lineno(function)
   500012.2670.0002.2670.000 :1(sendall)
   500011.2630.0001.2630.000 {method 'recv' of
'_socket.socket' objects}
   51.1120.0001.1120.000 {method 'insert' of 'list'
objects}
   500010.1370.0001.4900.000 Client.py:16(read_int)
   500010.1340.0002.4780.000 Client.py:8(send_int)
   10.0820.0822.6852.685 Client.py:19(read_int_list)
   500010.0770.0000.0770.000 struct.py:54(pack)
   500010.0730.0000.0890.000 struct.py:77(unpack)
   10.0440.0442.5222.522 Client.py:11(send_int_list)
   500010.0160.0000.0160.000 {method 'unpack' of
'Struct' objects}

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3629] Python won't compile a regex that compiles with 2.5.2 and 30b2

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

I came to the same conclusion: the 'skip' value is relative to the
previous code, so it is necessary to adjust the target position.
The patch is OK for me.

--
nosy: +amaury.forgeotdarc

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3743] PY_FORMAT_SIZE_T is not for PyString_FromFormat

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Jumping to "release blocker", since it causes a buildbot to fail.
Review needed.

--
priority:  -> release blocker

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3811] Update Unicode database to 5.1.0

[Marc-Andre Lemburg]

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment:

Reviewed the patch: looks fine to me. 

One nit: the unicodedata module doc-string must be updated to 5.1.0 as
well. Ditto for the documentation.

--
nosy: +lemburg

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3821] trace module bug when using --missing

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

This can be further simplified:
   line_increments = code.co_lnotab[1::2]

Assigning to myself, I will try to add unit tests as well. the trace
module is not tested at all...

--
assignee:  -> amaury.forgeotdarc
nosy: +amaury.forgeotdarc
priority:  -> critical

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3781] warnings.catch_warnings fails gracelessly when recording warnings but no warnings are emitted

[Nick Coghlan]

Nick Coghlan <[EMAIL PROTECTED]> added the comment:

Not quite that basic for the warnings.catch_warnings() part. I plan to
leave the current warnings.catch_warnings() alone (aside from adding
some re-entrancy checks), and add back a
test.test_support.check_warnings() that uses a WarningsRecorder object
to simplify the specific use cases in the Python regression test suite
(i.e. at least adding back the easy attribute access, and possibly other
things if there are other common features of the way we use it in the
tests).

The patch will make it clearer (working on that now).

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3825] Major reworking of Python 2.5.2 re module

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

The correct link is #2636.
Is it the same work?

--
nosy: +amaury.forgeotdarc

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1424152] urllib/urllib2: HTTPS over (Squid) Proxy fails

[Christian Kassab]

Christian Kassab <[EMAIL PROTECTED]> added the comment:

Python 2.4.3 also doesn't support ssl and a proxy to be used at the same
time in CentOS 5.1. This file addresses the issues. It has been tested
by using YUM to access a repository through a proxy using ssl client
certificates. YUM itself needed to be patched to allow for client certs
to be used... that change is on its way upstream.

Thanks to all the other guys here for supplying the first patches!

--
nosy: +ckassab
versions: +Python 2.4
Added file: http://bugs.python.org/file11454/issue1424152-py24.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3823] ssl.wrap_socket() is incompatible with servers that drop privileges, due to keyfile requirement

[Simon Cross]

Simon Cross <[EMAIL PROTECTED]> added the comment:

I've dug around in the code a bit and the keyfile, certfile and ca_certs
filename arguments to SSLSocket.__init__ are passed down into
newPySSLObject in _ssl.c and from there directly to SSL_CTX_* function
from OpenSSL so making these arguments allow file-like objects is going
to be non-trivial.

The options I see are:

* Write the file-like objects out to named temporary files and pass
those through to OpenSSL (seems like a nasty hack and prone to all sorts
of problems).

* Change the which OpenSSL functions are used to setup the certificate
(I definitely don't think this could go into 2.6 or 3.0 at this stage;
also see analysis of current OpenSSL usage below for more difficulties)

* Add an SSL CTX wrapper object and allow that to be passed down to
newPySSLObject instead of the filenames. Then the CTX object could be
created before dropping privileges (I think this is probably also too
big a change to be considered for 2.6 or 3.0 at this point, but it's
what looks best to me at the moment).

The current situation in _ssl.c:

* keyfile is loaded using SSL_CTX_use_PrivateKey_file(...) which loads
the first certificate from keyfile into ctx. We could replace this with
SSL_CTX_use_PrivateKey(SSL_CTX *ctx, EVP_PKEY *pkey) but we'd have to
load the key ourselves and make sure to follow what OpenSSL does to
maintain compatibility.

* certfile is loaded with SSL_CTX_use_certificate_chain_file(...) which
reads in all the certificates from certfile into ctx. We could read the
certificates in ourselves and them load them one by one using
SSL_CTX_use_certificate(...) and then SSL_CTX_add_extra_chain_cert(...).

* ca_certs is loaded using SSL_CTX_load_verify_locations(...). As fasr
as I can see there is no convenient replacement function for this in
OpenSSL. SSL_CTX_set_client_CA_list(...) will load a list of certificate
names but doesn't load the certificates themselves (so verification
won't be done with them) and SSL_CTX_add_client_CA(...) has the same
issue.  

One could use SSL_CTX_set_cert_store(...) to register callbacks (and
then presumably one can do whatever one wants and can get around the
ca_certs issue) but the man page for SSL_CTX_set_cert_store has the
rather disheartening "Currently no detailed documentation on how to use
the X509_STORE object is available."

All this comes with the proviso that I just started digging into the
OpenSSL manpages today so I'm a long way from being an expert. :)

I can probably find time to create a patch with tests once we have a
clear direction to go in.

@Forest: If you have an details on how non-Python servers go about
loading certificates and then dropping privileges using OpenSSL, that
would be extremely useful.

--
nosy: +hodgestar

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1606092] csv module broken for unicode

[Mike Statkus]

Mike Statkus <[EMAIL PROTECTED]> added the comment:

Example of UnicodeWriter.writerow(self,row) presented in Python 2.5
Manual at section 9.1.5 (Examples on CSV module of standard library)
does not correctly process rows containing not only strings, but also
int type values, raising an attribute error. 
1st line of code in UnicodeWriter.writerow:
self.writer.writerow([s.encode("utf-8") for s in row])
tries to call .encode() method for s, that might be an int, not a
string. A simple workaround is:
self.writer.writerow([unicode(s).encode("utf-8") for s in row])

--
nosy: +mstatkus

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3617] Add MS EULA to the list of third-party licenses in the Windows installer

[Travis N. Vaught]

Changes by Travis N. Vaught <[EMAIL PROTECTED]>:


--
nosy: +tvaught

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3824] test_tarfile fails on cygwin (unicode decode error)

[Hirokazu Yamamoto]

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment:

Sorry, probably I saw illusion... If uses cp932 codec, still
test_tarfile.py reports error. :-(

==
ERROR: test_tar_size (__main__.WriteTest)
--
Traceback (most recent call last):
  File "test_tarfile.py", line 570, in test_tar_size
tar.add(path)
  File "/home/WhiteRabbit/python-dev/py3k/Lib/tarfile.py", line 1953, in add
self.addfile(tarinfo, f)
  File "/home/WhiteRabbit/python-dev/py3k/Lib/tarfile.py", line 1976, in
addfile

buf = tarinfo.tobuf(self.format, self.encoding, self.errors)
  File "/home/WhiteRabbit/python-dev/py3k/Lib/tarfile.py", line 987, in
tobuf
return self.create_gnu_header(info, encoding, errors)
  File "/home/WhiteRabbit/python-dev/py3k/Lib/tarfile.py", line 1018, in
create_
gnu_header
return buf + self._create_header(info, GNU_FORMAT, encoding, errors)
  File "/home/WhiteRabbit/python-dev/py3k/Lib/tarfile.py", line 1107, in
_create
_header
stn(info.get("gname", "root"), 32, encoding, errors),
  File "/home/WhiteRabbit/python-dev/py3k/Lib/tarfile.py", line 177, in stn
s = s.encode(encoding, errors)
UnicodeEncodeError: 'ascii' codec can't encode characters in position
0-3: ordin
al not in range(128)

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3807] _multiprocessing build fails when configure --without-threads

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

The patch is not easy to read, but if it can be summarized to:

if sysconfig.get_config_var('WITH_THREAD'):

else:
missing.append('_multiprocessing')

then this makes sense - it seems that the multiprocessing module is
completely unusable if python cannot use threads. Even at the python
level, it uses "import threading" in many places.

This need another review, though. Raising issue to ReleaseBlocker.

--
nosy: +amaury.forgeotdarc
priority:  -> release blocker

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3824] test_tarfile fails on cygwin (unicode decode error)

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Is PyUnicode_DecodeMBCS available on cygwin?
I get compilation errors when I try your patch.

--
nosy: +amaury.forgeotdarc

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3824] test_tarfile fails on cygwin (unicode decode error)

[Hirokazu Yamamoto]

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment:

Yes, when I did it last night, I thought I could compile it and saw OK
on test_tarfile.py, but probably I dreamed. :-(

#define PyUnicode_FromString(s) PyUnicode_Decode(s, strlen(s), "cp932",
"strict")

or following patch should work.

--
keywords: +patch
Added file: http://bugs.python.org/file11455/experimental_mbcstowcs_codec.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3828] Bound methods compare 'successfully' with ints

[Andreas Kloeckner]

New submission from Andreas Kloeckner <[EMAIL PROTECTED]>:

Check out this transcript:
8< ---
Python 2.5.2 (r252:60911, Aug  8 2008, 09:22:44) 
[GCC 4.3.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> class A(object):
...   def b(self):
... pass
... 
>>> a = A()
>>> a.b < 0
False
>>> 
8< ---

I would argue that the 'successful' comparison of a bound method with an
int is undesirable. This especially bad when you're refactoring a class
property into a class method and the property used to get used in
comparisons.
Instead of the expected exceptions, you get weird behavior.

--
components: Interpreter Core
messages: 72961
nosy: inducer
severity: normal
status: open
title: Bound methods compare 'successfully' with ints
type: behavior
versions: Python 2.5

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3811] Update Unicode database to 5.1.0

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

I have now committed the change as r66362 (including the missing
documentation updates), and ported it to 3.0 as r66363 (where I had to
change the flag value and regenerate the data, as the flag 0x100 was
already taken).

--
resolution:  -> accepted
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3799] Byte/string inconsistencies between different dbm modules

[Guido van Rossum]

Guido van Rossum <[EMAIL PROTECTED]> added the comment:

I think this isn't quite right.

Ideally a fix should maintain several important properties:

(1) Be able to read databases written by Python 2.x.

(1a) Write databases readable by Python 2.x.

(2) Use the same mapping between str and bytes as the other *dbm
libraries have.

(2a) Return the same value for keys() as the other *dbm libraries
(except for order).

I think (2) means that we should use UTF-8 to convert str keys to bytes,
but (1) means we should use Latin-1 to convert keys to str *upon writing
the index*.  This will also satisfy (1a).  The keys maintained
internally should be kept in bytes to satsfy (2a).

PS. I noticed the dbm module still returns bytearrays for keys and
values. Is there a bug open to change those to bytes?

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3629] Python won't compile a regex that compiles with 2.5.2 and 30b2

[Guido van Rossum]

Guido van Rossum <[EMAIL PROTECTED]> added the comment:

Submitted as r66364.

I'll merge into 3.0 as well (it's  clean merge).

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

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3825] Major reworking of Python 2.5.2 re module

[Matthew Barnett]

Matthew Barnett <[EMAIL PROTECTED]> added the comment:

This is different work from a different author than #2636. I've
submitted what I've done so far in case my computer gets hit by a bus.
:-) I still have more work to do on it, so I'm not concerned that it
might not get any attention for a while.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3828] Bound methods compare 'successfully' with ints

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

You are right. And thanks to the time machine, python 3.0 already forbid
such comparisons:

>>> a.b < 0
Traceback (most recent call last):
  File "", line 1, in 
TypeError: unorderable types: method() < int()

The behaviour cannot change for the 2.x series, though - it would break
backward compatibility. python2.6 however has a "-3" option that prints
a warning in this case:

>>> a.b < 0
__main__:1: DeprecationWarning: comparing unequal types not supported in 3.x

--
nosy: +amaury.forgeotdarc
resolution:  -> works for me
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3781] warnings.catch_warnings fails gracelessly when recording warnings but no warnings are emitted

[Nick Coghlan]

Nick Coghlan <[EMAIL PROTECTED]> added the comment:

Cleanup patch now attached. Details of changes:

- warnings.catch_warnings() now has reentry guards (and associated
tests) to prevent silent errors when misused

- added back a test_support.check_warnings() convenience wrapper
(deliberately changing the name to be different from the context manager
in the warnings module). This wrapper is no longer configurable - it is
now used solely for tests that want to record normal warnings and check
the results.

- restored the w.reset() calls that went away in the previous checkin

- unit tests that want to test a different module, or don't want
warnings recorded now consistently use warnings.catch_warnings() directly

- cleanups up to the respective documentation

- cleanups to test_py3kwarn so it is better behaved when other tests are
run before it (the lack of reinitialisation of extension modules still
causes problems though)

- tested with "./python -3 -m test.regrtest -uall -x test_ossaudiodev"
(exclusion is needed because test_ossaudiodev hasn't worked properly on
my machine in a very long time - the audio file playback runs overtime
and I've never found the time to figure out why)

Just needs a review and then should be good to go.

--
keywords: +needs review -patch
Added file: 
http://bugs.python.org/file11456/issue3781_catch_warnings_cleanup.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3642] Objects/obmalloc.c:529: warning: comparison is always false due to limited range of data type

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

Here is my attempt for a patch (obmalloc.diff). Please review.

--
keywords: +needs review
Added file: http://bugs.python.org/file11457/obmalloc.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3743] PY_FORMAT_SIZE_T is not for PyString_FromFormat

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

The patch is fine, please apply.

--
assignee:  -> amaury.forgeotdarc
keywords:  -needs review
nosy: +loewis
resolution:  -> accepted

___
Python tracker <[EMAIL PROTECTED]>

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

[issue2876] Write UserDict fixer for 2to3

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

I still don't see why this is a release blocker. Adding a 2to3 fixer
certainly isn't a release blocker - if the fixer isn't available, users
would need to manually fix the code.

Adding a Py3k warning shouldn't be a release blocker, either - I think
such warnings could get added in 2.6.1 also (as they are only issued if
you invoke Python with -3).

Tentatively lowering the priority to normal.

--
nosy: +loewis
priority: release blocker -> normal

___
Python tracker <[EMAIL PROTECTED]>

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

[issue2350] 'exceptions' import fixer

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

Given that this is now a request for a fixer, and not a request for a
deprecation warning, I don't see why this is considered a release
blocker. Lowering the priority to normal. Even if the fixer isn't added
to the 2to3 copy shipped with 2.6.0, I think 2to3 improvements can well
be incorporated into 2.6.1 (including additional fixers).

--
nosy: +loewis
priority: release blocker -> normal

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3807] _multiprocessing build fails when configure --without-threads

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

Why is this a release blocker? If you configure without threads, you get
a few ugly compiler messages, but Python still builds exactly the same
way as without this patch, right?

So if the patch doesn't make it into 2.6, it can still be applied in
2.6.1 (as it is a clear bugfix).

Tentatively lowering priority to normal.

As for reviewing it: indeed, it looks overly complicated (perhaps it
would look nicer in Rietveld). As a last-minute change, I would prefer
something that looks more along the lines of Amaury's fragment (i.e.
trying to avoid changes to the indentation level).

--
nosy: +loewis
priority: release blocker -> normal

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1868] threading.local doesn't free attrs when assigning thread exits

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

If Christian's analysis is right, and memory is released except for the
last thread, I don't think this qualifies as a release blocker.

Also (unless I misinterpret the issue), it seems that we have made many
releases already which had this bug, so it's unclear why it should block
the next release.

Tentatively lowering the priority to high.

--
nosy: +loewis
priority: release blocker -> high

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3811] Update Unicode database to 5.1.0

[Guido van Rossum]

Changes by Guido van Rossum <[EMAIL PROTECTED]>:


Removed file: http://bugs.python.org/file11458/unnamed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3811] Update Unicode database to 5.1.0

[Guido van Rossum]

Guido van Rossum <[EMAIL PROTECTED]> added the comment:

2008/9/10 Martin v. Löwis <[EMAIL PROTECTED]>:
> I have now committed the change as r66362 (including the missing
> documentation updates), and ported it to 3.0 as r66363 (where I had to
> change the flag value and regenerate the data, as the flag 0x100 was
> already taken).

That's unfortunate -- perhaps the 2.6 flag and data can be brought in line,
to make future merges easier?

Added file: http://bugs.python.org/file11458/unnamed

___
Python tracker <[EMAIL PROTECTED]>

___2008/9/10 Martin v. Löwis [EMAIL 
PROTECTED]>:> I have now committed the change as r66362 
(including the missing> documentation updates), and ported it to 3.0 as 
r66363 (where I had to
> change the flag value and regenerate the data, as the flag 0x100 
was> already taken).That's unfortunate -- perhaps the 2.6 
flag and data can be brought in line, to make future merges easier?
-- --Guido van Rossum (home page: http://www.python.org/~guido/";>http://www.python.org/~guido/)
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3526] Customized malloc implementation on SunOS and AIX

[Sébastien Sablé]

Sébastien Sablé <[EMAIL PROTECTED]> added the comment:

My previous patch has a small problem as I believed dlmalloc was always
returning a non-NULL value, even when asking for 0 bytes.

It turns out not to be the case, so here is a new patch
(patch_dlmalloc3.diff) which must be applied after the previous one
(patch_dlmalloc2.diff) to correct this problem.

Added file: http://bugs.python.org/file11459/patch_dlmalloc3.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3823] ssl.wrap_socket() is incompatible with servers that drop privileges, due to keyfile requirement

[Bill Janssen]

Bill Janssen <[EMAIL PROTECTED]> added the comment:

Thanks, Simon.

I remember digging through all this last year, and finally deciding
to keep things simple and use the strategy the current codebase uses.

It almost sounds like we'd need to create Key and Certificate objects
in the _ssl module, which could be used to load up all the keys and/or
certificates the server uses, before it changes UID (and presumbably
loses access to the files the data is kept in).  I was resisting
going down that path; there's a lot of complexity there I want to avoid.
But much of the mechanism of a Certificate object is already there;
perhaps adding an opaque Key object wouldn't be too bad.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3823] ssl.wrap_socket() is incompatible with servers that drop privileges, due to keyfile requirement

[Jean-Paul Calderone]

Jean-Paul Calderone <[EMAIL PROTECTED]> added the comment:

Both M2Crypto and pyOpenSSL expose certificate and key objects and have
seen lots of real-world use.  Following their lead would be sensible.

--
nosy: +exarkun

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3756] re.escape() does not work with bytes()

[Guido van Rossum]

Guido van Rossum <[EMAIL PROTECTED]> added the comment:

Looks fine, except I used frozenset for the _alphanum* variables and
reverted to double quotes like the rest of the file.  Submitted as r66366.

--
assignee:  -> gvanrossum
resolution:  -> accepted
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3811] Update Unicode database to 5.1.0

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

> That's unfortunate -- perhaps the 2.6 flag and data can be brought in
> line, to make future merges easier?

I thought of that, however, merging the databases themselves would still
not be possible: the 3.0 database has the flags set in many records,
which causes merge conflicts (as the 2.x database has different flag
values). So regenerating the database is necessary, anyway.

In future changes, it might be useful to have new flags with the same
values, so that such patches can be merged without conflicts in the
generator.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3826] Self-reference in BaseHTTPRequestHandler descendants causes stuck connections

[romkyns]

romkyns <[EMAIL PROTECTED]> added the comment:

My initial description doesn't state the actual observable problem very
clearly: the problem is that the browser gets stuck instead of
displaying the page, writing something along the lines of "Transferring
data from localhost". After many seconds it times out. Aborting the
request in Firefox causes the page to be displayed.

Also forgot to mention that it's possible to work around this by
explicitly removing all circular references after the base class'
__init__ method - so for the attached example a work-around is
"self.dummy = None" as the last line of the __init__ method.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3829] Tuple comparison masking exception

[Fred L. Drake, Jr.]

New submission from Fred L. Drake, Jr. <[EMAIL PROTECTED]>:

There's a strange condition where cmp() of tuples of unorderable values
returns -1 even though using the unorderable values raises an exception.

If I have these two unorderable values, cmp() raises an expected exception:

  >>> s0 = frozenset(['testing 0'])
  >>> s1 = frozenset(['testing 1'])
  >>> cmp(s0, s1)
  Traceback (most recent call last):
File "", line 1, in ?
  TypeError: cannot compare sets using cmp()

Comparing tuples of the values returns -1:

  >>> cmp((s0,), (s1,))
  -1

Py3k does raise a TypeError, but the message is indecipherable:

  >>> cmp((s0,), (s1,))
  Traceback (most recent call last):
File "", line 1, in 
  TypeError: unorderable types: 'tuple' != 'tuple'

(The Py3k message for the set comparison is the same as for Python 2.)

I believe that this is an error; the exception from the underlying item
comparison should be propagated.

--
components: Interpreter Core
messages: 72981
nosy: fdrake
severity: normal
status: open
title: Tuple comparison masking exception
type: behavior
versions: Python 2.4, Python 2.5, Python 2.6, Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3823] ssl.wrap_socket() is incompatible with servers that drop privileges, due to keyfile requirement

[Bill Janssen]

Bill Janssen <[EMAIL PROTECTED]> added the comment:

Sure -- but the point of the SSL module was to do something
small and compatible with the existing socket.ssl module; I really don't
want to get into a full-fledged Python interface to OpenSSL.  Perhaps
incremental progress would be OK...

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3823] ssl.wrap_socket() is incompatible with servers that drop privileges, due to keyfile requirement

[Jean-Paul Calderone]

Jean-Paul Calderone <[EMAIL PROTECTED]> added the comment:

I'm just suggesting that if the ssl module *is* going to gain
certificate and key objects, looking at existing APIs and perhaps
emulating them, to the extent that they provide functionality which the
ssl module is also going to provide, is a good idea.  Perhaps we could
actually get the various APIs to begin to converge (where they overlap)
instead of producing further divergence.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1868] threading.local doesn't free attrs when assigning thread exits

[Gregory P. Smith]

Gregory P. Smith <[EMAIL PROTECTED]> added the comment:

Agreed, this is fine for a bugfix point release.

I was initially concerned about the Modules/threadmodule.c struct 
localobject changing but that is private and used only by code within 
threadmodule.c so its not part of an API anything else could depend on.  
Changing it for 2.6.1/2.5.3/3.0.1 should be fine.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3823] ssl.wrap_socket() is incompatible with servers that drop privileges, due to keyfile requirement

[Jean-Paul Calderone]

Jean-Paul Calderone <[EMAIL PROTECTED]> added the comment:

You can load a private key from a string by creating a memory BIO and
using PEM_read_bio_PrivateKey or d2i_PrivateKey_bio.

This is how pyOpenSSL implements its load_privatekey API.  You can see
the code here:

http://bazaar.launchpad.net/~exarkun/pyopenssl/trunk/annotate/70?file_id=crypto.c-20080219014912-qyb7kjf196jhzlyv-128

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3811] Update Unicode database to 5.1.0

[Daniel Diniz]

Daniel Diniz <[EMAIL PROTECTED]> added the comment:

#66363 breaks test_unicode and test_format on 3.0.

--
nosy: +ajaksu2
versions: +Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3823] ssl.wrap_socket() is incompatible with servers that drop privileges, due to keyfile requirement

[Forest Wilkinson]

Forest Wilkinson <[EMAIL PROTECTED]> added the comment:

Simon:  I wish I could offer guidance here, but I'm afraid that I too am
reading some of these openssl man pages for the first time.

I agree that writing to a temporary file would be bad.

Accepting file-like objects from python code would be nice, but isn't
really necessary.  Simple strings would suffice.  It's easy enough for
application code to read the strings from the appropriate files.  Of
course, the ssl module (or an underlying library) would need a way to
determine the data format within the strings.  Unfortunately, I didn't
notice an equivalent of SSL_CTX_use_PrivateKey_file() that accepts a
file's contents instead of its path.  SSL_CTX_use_RSAPrivateKey() looks
like the next best thing.

>much of the mechanism of a Certificate object is already there;
>perhaps adding an opaque Key object wouldn't be too bad."

That's encouraging.

>From the openssl docs I've read so far, it looks like certificates and
keys have several formats and use patterns.  That seems to me like
another argument in favor of supporting separate Certificate and Key
objects, even if they're only minimally implemented to begin with.  In
other words, I don't imagine the presence of Certificate and Key objects
would muck up the ssl module's api.

In order to keep compatibility with socket.ssl, perhaps any new
certificate and key objects should be accepted as alternatives to the
existing certfile and keyfile args, but the latter should still be allowed?

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3827] memoryview.size is redundant

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

Fixed in r66374.

--
resolution:  -> accepted
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3658] fix for pychecker property complaints

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

I agree with Antoine, so I'm just going to close this as rejected.
There's little benefit in it, but there is potential harm.

--
resolution:  -> rejected
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3640] test_cpickle crash on AMD64 Windows build

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Can someone have a look at this patch?
It is not 64bit nor Windows specific; its goal is to reduce the size of 
local variables in batch_list(), which is easy to verify.

The point is to check the correctness of the code, specially around 
errors checks and reference counting.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3743] PY_FORMAT_SIZE_T is not for PyString_FromFormat

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Committed r66377 and r66378.

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

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3743] PY_FORMAT_SIZE_T is not for PyString_FromFormat

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

You forgot to update Parser/asdl_c.py; I did it in r66379.

--
nosy: +benjamin.peterson

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3640] test_cpickle crash on AMD64 Windows build

[Benjamin Peterson]

Changes by Benjamin Peterson <[EMAIL PROTECTED]>:


--
nosy: +alexandre.vassalotti

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3830] Tarfile has incorrect USTAR "VERSION" field (should be 00; is 0 NUL)

[SunriseProgrammer]

New submission from SunriseProgrammer <[EMAIL PROTECTED]>:

The 'tarfile' object make incorrect header blocks.  There's a USTAR 
'MAGIC' string that's supposed to be followed by a version; that version 
is supposed to be two '0' (digit zero -- ascii 48) chars with no NUL 
padding at all.

Python 2.4.3 has it correct.  Later versions (e.g., 2.5) are carefully 
making the field NUL terminated -- but that's wrong; they aren't 
supposed to be.

File History:
'tarfile.py' was correct in version 41340 and incorrect in version 45954

--
components: Library (Lib)
messages: 72993
nosy: SunriseProgrammer
severity: normal
status: open
title: Tarfile has incorrect USTAR "VERSION" field (should be 00; is 0 NUL)
type: behavior
versions: Python 2.4, Python 2.5

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3830] Tarfile has incorrect USTAR "VERSION" field (should be 00; is 0 NUL)

[Benjamin Peterson]

Changes by Benjamin Peterson <[EMAIL PROTECTED]>:


--
assignee:  -> lars.gustaebel
nosy: +lars.gustaebel

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3642] Objects/obmalloc.c:529: warning: comparison is always false due to limited range of data type

[Brett Cannon]

Brett Cannon <[EMAIL PROTECTED]> added the comment:

Patch looks good to me and Martin's analysis of the test being useless
on a platform where size_t > uint_t makes sense.

--
keywords:  -needs review

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3781] warnings.catch_warnings fails gracelessly when recording warnings but no warnings are emitted

[Brett Cannon]

Brett Cannon <[EMAIL PROTECTED]> added the comment:

Code looks good.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3756] re.escape() does not work with bytes()

[Andrew McNamara]

Andrew McNamara <[EMAIL PROTECTED]> added the comment:

>Looks fine, except I used frozenset for the _alphanum* variables and
>reverted to double quotes like the rest of the file.  Submitted as r66366.

All good. Thankyou.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3811] Update Unicode database to 5.1.0

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Code point 0x0370 is now a printable character.
r66381 corrected the failures by simply changing it to 0x0378, until the 
next unicodedata upgrade...
I wonder if there is a value that is guaranteed to stay non-printable.

--
nosy: +amaury.forgeotdarc

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3821] trace module bug when using --missing

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Here is a simple test suite for the trace module, and two corrections to 
make it work.

The test file is suitable for 2.6 (simply replace test.support with 
test.test_support)

--
keywords: +needs review, patch
Added file: http://bugs.python.org/file11460/trace.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3827] memoryview.size is redundant

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

This causes test_ctypes to fail.
r66382 corrects the test to use len(v) instead of v.size

--
nosy: +amaury.forgeotdarc

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3811] Update Unicode database to 5.1.0

[Guido van Rossum]

Guido van Rossum <[EMAIL PROTECTED]> added the comment:

2008/9/10 Amaury Forgeot d'Arc <[EMAIL PROTECTED]>:
> Code point 0x0370 is now a printable character.
> r66381 corrected the failures by simply changing it to 0x0378, until the
> next unicodedata upgrade...
> I wonder if there is a value that is guaranteed to stay non-printable.

The control characters?

Added file: http://bugs.python.org/file11461/unnamed

___
Python tracker <[EMAIL PROTECTED]>

___2008/9/10 Amaury Forgeot d'Arc [EMAIL PROTECTED]>:> Code point 0x0370 is now a 
printable character.> r66381 corrected the failures by simply changing 
it to 0x0378, until the
> next unicodedata upgrade...> I wonder if there is a value that is 
guaranteed to stay non-printable.The control characters?-- 
--Guido van Rossum (home page: http://www.python.org/~guido/";>http://www.python.org/~guido/)

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

[issue3811] Update Unicode database to 5.1.0

[Guido van Rossum]

Changes by Guido van Rossum <[EMAIL PROTECTED]>:


Removed file: http://bugs.python.org/file11461/unnamed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3831] Multiprocessing: Expose underlying pipe in queues

[Steve Smith]

New submission from Steve Smith <[EMAIL PROTECTED]>:

Both Connection and Pipe objects expose their underlying file
descriptors, which is useful for accessing them in an event-driven
manner.  However the higher-level Queue does not make the underlying
pipe available; to get at them you must access private member attributes
which is fragile.  It would be good to have a well-defined API for
accessing either the pipe objects or the underlying FDs.

--
components: Extension Modules
messages: 73001
nosy: TarkaSteve
severity: normal
status: open
title: Multiprocessing: Expose underlying pipe in queues
type: feature request
versions: Python 2.6

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3831] Multiprocessing: Expose underlying pipe in queues

[Benjamin Peterson]

Changes by Benjamin Peterson <[EMAIL PROTECTED]>:


--
assignee:  -> jnoller
nosy: +jnoller

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3832] add force_shared Library option to create shared lib even with use_stub=False

[vajda]

New submission from vajda <[EMAIL PROTECTED]>:

setuptools is growing the capability to build regular shared libraries
(as opposed to python extensions). JCC
(http://svn.osafoundation.org/pylucene/trunk/jcc/jcc) uses this
capability to build the JCC runtime into a regular shared library shared
by all python extensions it builds and by programs embedding python
(such as a Java VM when running JCC-built eggs from Apache Tomcat).

This bug is about adding another option to the setuptools Library class
called force_shared which forces setuptools to create a shared library
from a Library instance even though the dl module may not be present to
generate stubs. This is important on Linux. Note that using this flag
then implies that the library itself is responsible for calling
dlopen(buf, RTLD_NOW | RTLD_GLOBAL) on the relevant libpython.so before
initializing the python runtime is initialized.

A patch against the setuptools 0.6 branch svn is attached.
The idea for this patch came from a conversation on IRC:
http://chandlerproject.org/script/getIrcTranscript.cgi?channel=chandler&date=20080910&startTime=1729

--
components: Distutils
files: patch.st
messages: 73002
nosy: pje, vajda
severity: normal
status: open
title: add force_shared Library option to create shared lib even with 
use_stub=False
type: feature request
Added file: http://bugs.python.org/file11462/patch.st

___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3832>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3833] python-2.6b3.msi and python-2.6b3.amd64.msi can't both be installed on one machine

[Jimmy Retzlaff]

New submission from Jimmy Retzlaff <[EMAIL PROTECTED]>:

I'm seeing the same symptoms that are described in issue 1543 with the
2.6b3 MSIs. Namely, when you run one of the MSIs (either 32-bit or
64-bit) then the other will refuse to install. This is on XP Pro x64 SP2.

python-3.0b3.msi and python-3.0b3.amd64.msi exhibit the same problem.

Having 32-bit and 64-bit version coexist makes it much easier to build
extensions for and test on both versions at the same time.

--
components: Installation, Windows
messages: 73003
nosy: jretz
severity: normal
status: open
title: python-2.6b3.msi and python-2.6b3.amd64.msi can't both be installed on 
one machine
type: feature request
versions: Python 2.6, Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3832] add force_shared Library option to create shared lib even with use_stub=False

[vajda]

vajda <[EMAIL PROTECTED]> added the comment:

This bug can be closed. It moved to the setuptools issue tracker as
issue 43.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3811] Update Unicode database to 5.1.0

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

> The control characters?

Indeed, also the private-use characters. test_unicode explicitly
comments that the test is about unassigned characters, although
I don't understand the purpose of that test (it then also tests
a surrogate character, which is also guaranteed to remain
unprintable).

One of the characters that is guaranteed to remain unassigned is
U+FFFE (and its mirrors in other planes, e.g. U+1FFFE, ...).
This guarantee is made to support the BOM. Along with U+,
these are non-characters. #765036 once suggested that Python should
refuse to represent them at all, but that proposal was rejected.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3832] add force_shared Library option to create shared lib even with use_stub=False

[Martin v. Löwis]

Changes by Martin v. Löwis <[EMAIL PROTECTED]>:


--
resolution:  -> invalid
status: open -> closed
versions: +3rd party

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1589] New SSL module doesn't seem to verify hostname against commonName in certificate

[Heikki Toivonen]

Heikki Toivonen <[EMAIL PROTECTED]> added the comment:

Ok, thank you for clarifications. Now I understand why the hostname
checking isn't the solution that fits every problem. I am still not
completely clear how you'd do the checking otherwise, for example to
verify the service you are talking to is what you think it is.

But still, I think dealing with email servers is another common use case
where hostname check is adequate most of the time. I am sure there are
other cases like this. Therefore I am still of the opinion that the
default should be to do the hostname check. Yes, make it overridable,
but doing the check is safer than not doing any checking IMO because
even if the check is incorrect for a certain purpose the developer is
likely to notice an error quickly and inclined to do some other security
check instead of not doing anything and thinking they have a secure system.

If you want to continue the discussion, we should maybe take this to
some other forum, like comp.lang.python.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3642] Objects/obmalloc.c:529: warning: comparison is always false due to limited range of data type

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

I have now committed the new patch as r66383 and r66384

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

___
Python tracker <[EMAIL PROTECTED]>

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