[issue2532] file that breaks 2to3 (despite being correct python)

[Mark Hammond]

Mark Hammond <[EMAIL PROTECTED]> added the comment:

pywin32 has a number of files that break in this way - often files
generated by h2py.py

--
nosy: +mhammond

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3994] import fixer misses some symbols

[Mark Hammond]

New submission from Mark Hammond <[EMAIL PROTECTED]>:

The following source file:
"""
import _winreg
_winreg.OpenKey(_winreg.HKEY_LOCAL_MACHINE, "foo")
"""

results in the following "patch":

-import _winreg
-_winreg.OpenKey(_winreg.HKEY_LOCAL_MACHINE, "foo")
+import winreg
+winreg.OpenKey(_winreg.HKEY_LOCAL_MACHINE, "foo")

Note the first param has not been converted correctly.  This is probably
due to it following the paren, as using the same symbol in a local
variable works correctly.

--
components: 2to3 (2.x to 3.0 conversion tool)
messages: 74014
nosy: mhammond
priority: high
severity: normal
status: open
title: import fixer misses some symbols
type: behavior

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3941] Help in IDLE should open the chm file

[Georg Brandl]

Changes by Georg Brandl <[EMAIL PROTECTED]>:


--
resolution:  -> wont fix
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

[issue3770] test_multiprocessing fails on systems with HAVE_SEM_OPEN=0

[Nick Coghlan]

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

Agreed - Jesse, can you work up a patch that generates a clean import
error when _multiprocessing.SemLock can't be defined (due to
HAVE_SEM_OPEN=0 or a single-threaded build), adds test_multiprocessing
to the expected skips for FreeBSD and OpenBSD, and updates the
multiprocessing docs to note the restriction to systems with a working
sem_open() implementation?

Improving the *BSD and single-threaded build compatibility of the
multiprocessing package will just have to be high on the to-do list for
2.6.1.

This may also be worth mentioning in the release notes - Barry's call on
that one.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3984] python interpreter import dependency with disutils/util

[Tarek Ziadé]

Tarek Ziadé <[EMAIL PROTECTED]> added the comment:

Well, I have a patch in progress, that pulls it out in another package.
But I still get problems with the logging dependency, so it seems like a
lot of extra work for just this use case.

On the other hand, if distutils is going to be "cleaned" in the future,
this would probably be a good thing to extract those elements.

I am attaching a patch I have started just for the record, if something
is changed one day. It works besides the logging dependency and it shows
how it could be split maybe.

--
keywords: +patch
versions: +Python 2.7 -Python 2.6
Added file: http://bugs.python.org/file11651/split-low-level-concerns.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3992] removed custom log from distutils

[Tarek Ziadé]

Changes by Tarek Ziadé <[EMAIL PROTECTED]>:


--
versions: +Python 2.7, Python 3.1 -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

[issue3987] removed types from distutils.core [patch]

[Tarek Ziadé]

Changes by Tarek Ziadé <[EMAIL PROTECTED]>:


--
versions: +Python 2.7, Python 3.1 -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

[issue3986] removed string and type usage from distutils.cmd [patch]

[Tarek Ziadé]

Changes by Tarek Ziadé <[EMAIL PROTECTED]>:


--
versions: +Python 2.7, Python 3.1 -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

[issue3985] removed string module from distutils [patch]

[Tarek Ziadé]

Changes by Tarek Ziadé <[EMAIL PROTECTED]>:


--
versions: +Python 2.7, Python 3.1 -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

[issue2461] test_util.py for distutils

[Tarek Ziadé]

Changes by Tarek Ziadé <[EMAIL PROTECTED]>:


--
versions: +Python 2.7, Python 3.1 -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

[issue3995] iso-xxx/cp1252 inconsistencies in Python 2.* not in 3.*

[Jean-Michel Fauth]

New submission from Jean-Michel Fauth <[EMAIL PROTECTED]>:

XP SP2 fr_CH cp1252

I have always found, there are some inconsistencies in the Python <=2.5
serie regarding the char endodings, especially the iso-8859-1, cp1252,
iso-8859-15 encodings.

I do not know if this must be considered as a bug or as a feature.
Python is quite friendly with these encodings. It may not be a problem
for a daily work, it is more acute when one wish to teach the
chararacter encodings.

char "œ": "code point" 156 in cp1252
char "€": "code point" 128 in cp1252

Python 2.5.2

>>> unicode('œ', 'cp1252')
u'\u0153'
>>> unicode('€', 'cp1252')
u'\u20ac'
>>> unicode('œ', 'iso-8859-15')
u'\x9c'
>>> unicode('€', 'iso-8859-15')
u'\x80'
>>> unicode('€', 'iso-8859-1') #***
u'\x80'
>>> unicode('œ', 'iso-8859-1') #***
u'\x9c'
>>> #*** should raise an error since œ and €
>>> #are not existing in an iso-8859-1 table.
>>> 

It looks like iso-8859-1 behaves as iso-8859-15 (typo somewhere?)

Python 3.0 rc1 does the job correctly and notices the difference

>>> bytes('œ', 'cp1252')
b'\x9c'
>>> bytes('€', 'cp1252')
b'\x80'
>>> bytes('œ', 'iso-8859-15')
b'\xbd'
>>> bytes('€', 'iso-8859-15')
b'\xa4'
>>> bytes('œ', 'iso-8859-1')
Traceback (most recent call last):
  File "", line 1, in 
bytes('œ', 'iso-8859-1')
UnicodeEncodeError: 'latin-1' codec can't encode character '\u0153' in
position 0: ordinal not in range(256)
>>> bytes('€', 'iso-8859-1')
Traceback (most recent call last):
  File "", line 1, in 
bytes('€', 'iso-8859-1')
UnicodeEncodeError: 'latin-1' codec can't encode character '\u20ac' in
position 0: ordinal not in range(256)
>>> # these errors are expected
>>> 

Python 2.6**

The latest version is not installed. If I recall correcly, 2.6b* are
presenting the same issue as in 2.5.2 .

--
messages: 74017
nosy: jmfauth
severity: normal
status: open
title: iso-xxx/cp1252  inconsistencies in Python 2.* not in 3.*
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

[issue3995] iso-xxx/cp1252 inconsistencies in Python 2.* not in 3.*

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

If you write "€" in the Python interpreter (Python2), you will get a 
*bytes* string encoded in your terminal charset. Example on Linux 
(utf-8):

Python 2.5.1 (r251:54863, Jul 31 2008, 23:17:40)
>>> '€'
'\xe2\x82\xac'

Use "u" prefix to get unicode string:

Python 2.5.1 (r251:54863, Jul 31 2008, 23:17:40)
>>> u'€'
u'\u20ac'

If you use unicode, encoding to ISO-8859-1/-15 works correctly. 
(Truncated) example with python trunk:

Python 2.6rc2+ (trunk:66680M, Sep 29 2008, 12:03:32)
>>> u'€'.encode('ISO-8859-1')
...
UnicodeEncodeError: 'latin-1' codec can't encode character u'\u20ac'
>>> u'€'.encode('ISO-8859-15')
'\xa4'

In a script (Python code written in a file), use #coding header to 
specify your file charset. Or use "\xXX", "\u" and "\U" 
notations for non-ASCII characters.

Is there somewhere an Unicode Python FAQ? :-)

--
nosy: +haypo

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3982] support .format for bytes

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

I don't think that b'...'.format() is a good idea. Programmers will 
continue to mix characters and bytes since .format() target are 
characters.

--
nosy: +haypo

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1069092] segfault on printing nested sequences of None/Ellipsis

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

This issue is a stack overflow: your code do recursive calls to 
internal_print().

Backtrace from gdb:

#0  0xb7e92064 in _IO_new_file_overflow () 
from /lib/tls/i686/cmov/libc.so.6
#1  0xb7e94bc3 in __overflow () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7e8e03b in fputc () from /lib/tls/i686/cmov/libc.so.6
#3  0x080a2f2d in tupleprint (op=0xb7b5cc2c, fp=0xb7f744e0, flags=0) 
at Objects/tupleobject.c:193
#4  0x0808b9f7 in internal_print (op=0xb7b5cc2c, fp=0xb7f744e0, 
flags=0, nesting=0) at Objects/object.c:309
#5  0x0808ba60 in PyObject_Print (op=0xb7b5cc2c, fp=0xb7f744e0, 
flags=0) at Objects/object.c:324
(...)
#4628 0x0808ba60 in PyObject_Print (op=0xb7b68e4c, fp=0xb7f744e0, 
flags=0) at Objects/object.c:324
#4629 0x080a2f9e in tupleprint (op=0xb7b68e6c, fp=0xb7f744e0, flags=0) 
at Objects/tupleobject.c:201
#4630 0x0808b9f7 in internal_print (op=0xb7b68e6c, fp=0xb7f744e0, 
flags=0, nesting=0) at Objects/object.c:309
#4631 0x0808ba60 in PyObject_Print (op=0xb7b68e6c, fp=0xb7f744e0, 
flags=0) at Objects/object.c:324
(...)
#4638 0x080a2f9e in tupleprint (op=0xb7b68ecc, fp=0xb7f744e0, flags=0) 
at Objects/tupleobject.c:201
#4639 0x0808b9f7 in internal_print (op=0xb7b68ecc, fp=0xb7f744e0, 
flags=0, nesting=0) at Objects/object.c:309
#4640 0x0808ba60 in PyObject_Print (op=0xb7b68ecc, fp=0xb7f744e0, 
flags=0) at Objects/object.c:324
#4641 0x080a2f9e in tupleprint (op=0xb7b68eec, fp=0xb7f744e0, flags=0) 
at Objects/tupleobject.c:201
#4642 0x0808b9f7 in internal_print (op=0xb7b68eec, fp=0xb7f744e0, 
flags=0, nesting=0) at Objects/object.c:309
(...)


Informations using my debugger (python-ptrace):

PID: 1201
Signal: SIGSEGV
STACK OVERFLOW! Stack pointer is in 0xbf10d000-0xbf90d000 => [stack] 
(rw-p)
- instruction: CALL 0x80d3305
- mapping: 0xbf10cff0 is not mapped in memory
- register =0xbf10cff0


Some solutions:
 - avoid creation of nested sequence
 - create generic protection against stack overflow (use 
setjmp/longjmp)
 - avoid recursive call to internal_print()

--
nosy: +haypo

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3982] support .format for bytes

[Eric Smith]

Eric Smith <[EMAIL PROTECTED]> added the comment:

> I don't think that b'...'.format() is a good idea. Programmers
> will continue to mix characters and bytes since .format() target
> are characters.

b''.format() would return bytes, not a string. This is also how it works
in 2.6.

I'm also not sold on implementing it, although it would be easy and I
can see a few uses for it. I think Martin's suggesting of encoding back
to ascii might be the best thing to do (that is, don't implement
b''.format()).

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3982] support .format for bytes

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

> I think Martin's suggesting of encoding back to ascii might be 
> the best thing to do

As I understand, you would like to use bytes as characters, like 
b'{code} {message}'.format(code=100, message='OK'). So why no using 
explicit conversion to ASCII? ftp='{code} {message}'.format(code=100, 
message='OK').encode('ASCII').

If you need to work on bytes, it means that you will use the full 
range 0..255 whereas ASCII reject bytes in 128..255.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3977] Check PyInt_AsSsize_t/PyLong_AsSsize_t error

[Amaury Forgeot d'Arc]

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

All these patches seem good to me.

--
nosy: +amaury.forgeotdarc
priority:  -> high

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3996] PyOS_CheckStack does not work

[Amaury Forgeot d'Arc]

New submission from Amaury Forgeot d'Arc <[EMAIL PROTECTED]>:

On Windows, PyOS_CheckStack is supposed to protect the interpreter from
stack overflow. But doing this, it always crashes when the stack is
nearly full.

The reason is a bad check of the return value of _resetstkoflw():
according to MSDN, the return value is "Nonzero if the function
succeeds, zero if it fails.":
http://msdn.microsoft.com/en-us/library/89f73td2.aspx

The patch below is enough to replace the "Fatal Python error: Could not
reset the stack!" into a "MemoryError: stack overflow" exception.

Tested with:
>>> loop = None,
>>> for x in xrange(10): loop = {'x': loop}
...
>>> len(repr(loop))



Index: Python/pythonrun.c
===
--- Python/pythonrun.c  (revision 66486)
+++ Python/pythonrun.c  (working copy)
@@ -1749,7 +1755,7 @@
EXCEPTION_EXECUTE_HANDLER :
EXCEPTION_CONTINUE_SEARCH) {
int errcode = _resetstkoflw();
-   if (errcode)
+   if (errcode == 0)
{
Py_FatalError("Could not reset the stack!");
}

--
assignee: loewis
components: Windows
keywords: patch
messages: 74024
nosy: amaury.forgeotdarc, loewis
severity: normal
status: open
title: PyOS_CheckStack does not work
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

[issue2636] Regexp 2.7 (modifications to current re 2.2.2)

[Jeffrey C. Jacobs]

Jeffrey C. Jacobs <[EMAIL PROTECTED]> added the comment:

Good work, Matthew.  Now, another bazaar hint, IMHO, is once of my
favourite commands: switch.  I generally develop all in one directory,
rather than getting a new directory for each branch.  Once does have to
be VERY careful to type "bzr info" to make sure the branch you're
editing is the one you think it is! but with "bzr switch", you do a
differential branch switch that allows you to change your development
branch quickly and painlessly.  This assumes you did a "bzr checkout"
and not a "bzr pull".  If you did a pull, you can still turn this into a
"checkout", where all VCS actions are mirrored on the server, by using
the 'bind' command.  Make sure you push your branch first.  You don't
need to worry about all this "bind"ing, "push"ing and "pull"ing if you
choose checkout, but OTOH, if your connection is over-all very slow, you
may still be better off with a "pull"ed branch rather than a
"checkout"ed one.

Anyway, good catch on those 4 lines and I'll see if I can get your
earlier branches up to date.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue2636] Regexp 2.7 (modifications to current re 2.2.2)

[Jeffrey C. Jacobs]

Jeffrey C. Jacobs <[EMAIL PROTECTED]> added the comment:

Matthew, I've traced down the patch failures in my merges and now each
of the 4 versions of code on Launchpad should compile, though the first
2 do not pass all the negative look-behind tests, though your later 2
do.  Any chance you could back-port that fix to the
lp:~pythonregexp2.7/python/issue2636-01+09-02+17 branch?  If you can, I
can propagate that fix to the higher levels pretty quickly.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3995] iso-xxx/cp1252 inconsistencies in Python 2.* not in 3.*

[Georg Brandl]

Changes by Georg Brandl <[EMAIL PROTECTED]>:


--
resolution:  -> invalid
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

[issue3187] os.listdir can return byte strings

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

About os.getcwd(), another solution is merge_os_getcwd_getcwdu.patch: 
os.getcwd() always return unicode string and raise an error on unicode 
decode error. Wheras os.getcwd(bytes=True) always return bytes. 

The old function os.getcwdu() is removed since os.getcwd() already 
return unicode string.

Note: current version of os.getcwd() uses the wrong encoding to 
conversion bytes to unicode: it uses PyUnicode_FromString() instead of 
PyUnicode_Decode(..., Py_FileSystemDefaultEncoding, "strict") (as does 
getcwdu()).

Added file: http://bugs.python.org/file11652/merge_os_getcwd_getcwdu.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3944] faster long multiplication

[Pernici Mario]

Pernici Mario <[EMAIL PROTECTED]> added the comment:

Mark, following your suggestions about using bigger integer types,
I added code to convert Python numbers to arrays of twodigits,
when a 64 bit integer type is supported, and for numbers with size
larger than 20; otherwise the code of the previous patch is used.
This 64 bit integer is used only inside multiplication, so no
modifications need to be made in other parts of the Python code.
Now with numbers with 300 decimal digits or more the speedup is
2x on 32 bit machine, 3x on 64 bit machine (50% and 2x respectively
for squaring).

There is a macro HAVE_INT64 to control if there is a 64 bit type;
the preprocessor instructions should be OK with gcc, but other
compilers might have a 64 bit type and not long long, so HAVE_INT64
is wrongly not defined and one falls back to multiplying arrays of
16 bit digits; these preprocessor instructions need to be fixed.

The speed difference for small integers is small;
here is a summary of some benchmarks on
Pentium M 1.6GHz, Athlon XP 2600+,
Athlon 64 X2 Dual Core 3800+, all with Debian;
speedup of this patch with respect to the current revision
(+ means the patch is faster):
In pybench, SimpleIntegerArithmetic: from -0.5% to +0.5%
SimpleLongArithmetic:  : from -1% to +7%
pystone: from +0.5% to +1.5%

Added file: http://bugs.python.org/file11653/longobject2.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3944] faster long multiplication

[Mark Dickinson]

Mark Dickinson <[EMAIL PROTECTED]> added the comment:

Nice work!  Seems like we're going to be able to look forward to faster 
integer arithmetic in Python 2.7 / 3.1.  I'll try to find time to review 
your patch properly sometime soon.

Regarding the HAVE_INT64, there's a standard autoconf macro 
AC_TYPE_INT64_T (and its unsigned counterpart AC_TYPE_UINT64_T) that 
automatically sets int64_t (or uint64_t) to a 64-bit (unsigned) integer 
type whenever it exists.  So don't worry about the preprocessor stuff for 
the moment, so long as it's working on your machine;  we can fix it in 
Python's configure script instead sometime.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3187] os.listdir can return byte strings

[Raghuram Devarakonda]

Changes by Raghuram Devarakonda <[EMAIL PROTECTED]>:


--
nosy: +draghuram

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3997] zipfile and winzip

[vali]

New submission from vali <[EMAIL PROTECTED]>:

using ZipFile library with Python 2.6 or an earlier version creates
archived files that are not compatible with windows compress or Winzip.
Other programs like 7-Zip will not have a problem with the format. 

Bug Description:
if it is attempted to create an archive with more than 65535 (e.g 2^16 +
10)  files winzip or windows compress will show only what is above 65535
(in this case 9 file) 

The attached script tries to create an archive with 2^16 + 1 files and
compress or winzip will show an empty archive.

--
components: Extension Modules
files: bug.py
messages: 74030
nosy: vgeorge
severity: normal
status: open
title: zipfile and winzip
type: behavior
versions: Python 2.6
Added file: http://bugs.python.org/file11654/bug.py

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3997] zipfile and winzip

[Amaury Forgeot d'Arc]

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

An archive with more than 65535 files must use the "64-bit extensions"
of the standard Zip format.

Such archives cannot be opened by programs that do not understand these
extensions. See http://www.winzip.com/wzdic.htm

Which version of Winzip did you try?

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

[issue3187] os.listdir can return byte strings

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

As Steven Bethard proposed, here is a new version of my getcwd() 
patch: instead of adding a keyword argument "bytes", I created a 
function getcwdb():
 * os.getcwd() -> unicode
 * os.getcwdb() -> bytes

In Python2 it was:
 * os.getcwd() -> str (bytes)
 * os.getcwdu() -> unicode

Added file: http://bugs.python.org/file11655/os_getcwdb.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3910] 2.6 regression in socket.ssl method

[Bill Janssen]

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

Will do.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3910] 2.6 regression in socket.ssl method

[Bill Janssen]

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

Maybe not.  test_ssl hangs when I run it "-u all -v".  It's hanging on
testSimpleSSLWrap.  This is on OS X 10.5.5.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3944] faster long multiplication

[Christian Heimes]

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

Nice work :)

I'm changing the target versions to 2.7 and 3.1. The proposed changes
are too large for a maintenance release.

--
components: +Interpreter Core
nosy: +christian.heimes
priority:  -> high
versions: +Python 2.7, Python 3.1 -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

[issue3770] test_multiprocessing fails on systems with HAVE_SEM_OPEN=0

[Jesse Noller]

Jesse Noller <[EMAIL PROTECTED]> added the comment:

Hows this error look:

>>> import multiprocessing
Traceback (most recent call last):
  File "", line 1, in 
  File "/Users/jesse/open_source/subversion/python-
trunk/Lib/multiprocessing/__init__.py", line 178, in 
" function, see issue 3770.")
multiprocessing.SemaphoreImportError: This platform lacks a functioning 
sem_open implementation and thereforce, the required synchronization 
primitives needed will not function, see issue 3770.
>>>

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3770] test_multiprocessing fails on systems with HAVE_SEM_OPEN=0

[Damien Miller]

Damien Miller <[EMAIL PROTECTED]> added the comment:

looks good to me

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3894] imageop issue

[Brett Cannon]

Changes by Brett Cannon <[EMAIL PROTECTED]>:


--
assignee:  -> benjamin.peterson
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

[issue3984] python interpreter import dependency with disutils/util

[Brett Cannon]

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

On Sun, Sep 28, 2008 at 7:56 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
>
> Benjamin Peterson <[EMAIL PROTECTED]> added the comment:
>
> Brett, are you looking for #586680?
>

Yep, that's the issue.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3910] 2.6 regression in socket.ssl method

[Bill Janssen]

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

OK, I found the fix.

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

[issue3770] test_multiprocessing fails on systems with HAVE_SEM_OPEN=0

[Brett Cannon]

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

On Mon, Sep 29, 2008 at 11:20 AM, Jesse Noller <[EMAIL PROTECTED]> wrote:
>
> Jesse Noller <[EMAIL PROTECTED]> added the comment:
>
> Hows this error look:
>
 import multiprocessing
> Traceback (most recent call last):
>  File "", line 1, in 
>  File "/Users/jesse/open_source/subversion/python-
> trunk/Lib/multiprocessing/__init__.py", line 178, in 
>" function, see issue 3770.")
> multiprocessing.SemaphoreImportError: This platform lacks a functioning
> sem_open implementation and thereforce, the required synchronization
> primitives needed will not function, see issue 3770.

Is "thereforce" an actual word? Otherwise it looks fine to me.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3770] test_multiprocessing fails on systems with HAVE_SEM_OPEN=0

[Jesse Noller]

Jesse Noller <[EMAIL PROTECTED]> added the comment:

> Is "thereforce" an actual word? Otherwise it looks fine to me.
>

Yeah, I caught that. Rather than disable the entire package, which
would be frustrating to many - I've changed it to only disable
mp.synchronize for now, patch is pending my final build and test/doc
check locally

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3547] Ctypes is confused by bitfields of varying integer types

[Thomas Heller]

Thomas Heller <[EMAIL PROTECTED]> added the comment:

Committed as SVN rev 66683 (trunk), 66684 (py3k), and 66685
(release25-maint).

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

[issue3770] test_multiprocessing fails on systems with HAVE_SEM_OPEN=0

[Jesse Noller]

Jesse Noller <[EMAIL PROTECTED]> added the comment:

Here's a patch, works on my machine. Please review it and make sure it 
satisfies what we've spoken about.

--
keywords: +needs review, patch
Added file: http://bugs.python.org/file11656/issue3770.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3996] PyOS_CheckStack does not work

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

This issue may be related: issue1069092

--
nosy: +haypo

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3770] test_multiprocessing fails on systems with HAVE_SEM_OPEN=0

[Nick Coghlan]

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

Could use confirmation from Damien and Andrew that they now see the
expected skips with the patch applied, but otherwise looks good to me.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3991] urllib.request.urlopen does not handle non-ASCII characters

[Bill Janssen]

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

As I read RFC 2396,

1.5:  "A URI is a sequence of characters from a very
   limited set, i.e. the letters of the basic Latin alphabet, digits,
   and a few special characters."

2.4:  "Data must be escaped if it does not have a representation using an
   unreserved character; this includes data that does not correspond to
   a printable character of the US-ASCII coded character set, or that
   corresponds to any US-ASCII character that is disallowed, as
   explained below."

So your URL string is invalid.  You need to escape the characters properly.

(RFC 2396 is what the HTTP RFC cites as its authority on URLs.)

--
nosy: +janssen

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1745035] DoS smtpd vulnerability

[Josiah Carlson]

Josiah Carlson <[EMAIL PROTECTED]> added the comment:

The patch does not work as Giampaolo intends.  If the patch were applied 
as-is, no emails longer than 998 bytes could be sent.

Instead, incrementing linelen in the collect_incoming_data() method 
should only be performed if self.terminator == '\r\n'.

I can apply a modified version of this patch against trunk after 2.6 is 
released.  Backports to 2.5 and 2.6 should then be discussed.

--
assignee: barry -> josiahcarlson
nosy: +josiahcarlson

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3956] turtle.py - bug in Screen.__init__()

[Martin v. Löwis]

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

> When 2.6 is out, what do you think is the right point for a further
> discussion of this? (I think certainly not the bugtracker and
> particularly not this issue.

Depends on what you want to achieve with the discussion. If you want
a public opinion, post to comp.lang.python. Most likely, the public
doesn't care - at least not so much to spend actually time trying to
understand the issue.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3995] iso-xxx/cp1252 inconsistencies in Python 2.* not in 3.*

[Martin v. Löwis]

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

 unicode('€', 'iso-8859-15')
> u'\x80'
 unicode('€', 'iso-8859-1') #***
> u'\x80'
> 
> It looks like iso-8859-1 behaves as iso-8859-15 (typo somewhere?)

That's correct, and intentional. iso-8850-1 and iso-8859-15 are
*indeed* the same for the respective code points (i.e \x80 and
\x9c).

--
nosy: +loewis
title: iso-xxx/cp1252  inconsistencies in Python 2.* not in 3.* -> 
iso-xxx/cp1252 inconsistencies inPython 2.* not in 3.*

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3977] Check PyInt_AsSsize_t/PyLong_AsSsize_t error

[Benjamin Peterson]

Changes by Benjamin Peterson <[EMAIL PROTECTED]>:


--
assignee:  -> benjamin.peterson
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

[issue3982] support .format for bytes

[Martin v. Löwis]

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

>> I think Martin's suggesting of encoding back to ascii might be 
>> the best thing to do
> 
> As I understand, you would like to use bytes as characters, like 
> b'{code} {message}'.format(code=100, message='OK'). So why no using 
> explicit conversion to ASCII? ftp='{code} {message}'.format(code=100, 
> message='OK').encode('ASCII').

That's indeed exactly what I had proposed - only that you shouldn't
repeat the .encode('ascii') all over the place, but instead wrap that
into a function (which I proposed to call push_string, along with the
existing .push function.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3956] turtle.py - bug in Screen.__init__()

[Martin v. Löwis]

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

Committed (with the two proposed modifications) as r66686 and r66687.

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

[issue3996] PyOS_CheckStack does not work

[Amaury Forgeot d'Arc]

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

Yes, issue1069092 is another case where PyOS_CheckStack is exercised. 
But this other issue was first reported on Unix, when PyOS_CheckStack is 
currently implemented only for Windows.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3991] urllib.request.urlopen does not handle non-ASCII characters

[Toshio Kuratomi]

Toshio Kuratomi <[EMAIL PROTECTED]> added the comment:

Possibly.  This is a change from python-2.x's urlopen() which escaped
the URL automatically, though.  I can see the case for having the user
call an escape function themselves instead of having urlopen() perform
the escape for them.  However, that function would need to be written.
(The present parse.quote() method only quotes correctly if only the path
component is passed; there's no function to take a full URL and quote it
appropriately.)

Without such a function, a whole lot of code bases will have to reinvent
the wheel creating functions to parse the path out, run it through
urllib.parse.quote() and then pass the result to urlib.urlopen().

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3770] test_multiprocessing fails on systems with HAVE_SEM_OPEN=0

[Damien Miller]

Damien Miller <[EMAIL PROTECTED]> added the comment:

I can confirm that the patch works on OpenBSD -current. Only one nit:

Does this line in Lib/test/test_multiprocessing.py need to be there?

+#import multiprocessing.SemaphoreImportError

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3770] test_multiprocessing fails on systems with HAVE_SEM_OPEN=0

[Jesse Noller]

Jesse Noller <[EMAIL PROTECTED]> added the comment:

On Sep 29, 2008, at 6:36 PM, Damien Miller <[EMAIL PROTECTED]>  
wrote:

>
> Damien Miller <[EMAIL PROTECTED]> added the comment:
>
> I can confirm that the patch works on OpenBSD -current. Only one nit:
>
> Does this line in Lib/test/test_multiprocessing.py need to be there?
>
> +#import multiprocessing.SemaphoreImportError
>

Oops - my bad. I'll remove it and check it tonight

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3998] List.sort docstring has obsolete cmp reference.

[Terry J. Reedy]

New submission from Terry J. Reedy <[EMAIL PROTECTED]>:

3.0rc1
>>> help(list.sort)
Help on method_descriptor:

sort(...)
L.sort(key=None, reverse=False) -- stable sort *IN PLACE*;
cmp(x, y) -> -1, 0, 1

The last line is left over from 2.x docstring.  Since cmp keyword param
is gone (so also says LibRef: "s.sort([key[, reverse]]) sort the items
of s in place") delete it.

--
assignee: georg.brandl
components: Documentation
keywords: easy
messages: 74056
nosy: georg.brandl, tjreedy
severity: normal
status: open
title: List.sort docstring has obsolete cmp reference.
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

[issue3770] test_multiprocessing fails on systems with HAVE_SEM_OPEN=0

[Jesse Noller]

Jesse Noller <[EMAIL PROTECTED]> added the comment:

checked in r66688, lowering from rb to crit to address post 2.6 final

--
priority: release blocker -> critical

___
Python tracker <[EMAIL PROTECTED]>

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

[issue2636] Regexp 2.7 (modifications to current re 2.2.2)

[Matthew Barnett]

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

issue2636-01+09-02+17_backport.diff is the backport fix.

Still unable to compress the download, so that's >200MB each time!

Added file: http://bugs.python.org/file11657/issue2636-01+09-02+17_backport.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3187] os.listdir can return byte strings

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

Patch python3_bytes_filename.patch:
 - open() support bytes
 - listdir(unicode) -> only unicode, *skip* invalid filenames 
   (as asked by Guido)
 - remove os.getcwdu()
 - create os.getcwdb() -> bytes
 - glob.glob() support bytes
 - fnmatch.filter() support bytes
 - posixpath.join() and posixpath.split() support bytes

Mixing bytes and str is invalid. Examples raising a TypeError:
 - posixpath.join(b'x', 'y')
 - fnmatch.filter([b'x', 'y'], '*')
 - fnmatch.filter([b'x', b'y'], '*')
 - glob.glob1('.', b'*')
 - glob.glob1(b'.', '*')

TODO:
 - review this patch :-)
 - support non-ASCII bytes in fnmatch.filter()
 - fix other functions, eg. posixpath.isabs() and 
fnmatch.fnmatchcase()
 - fix functions written in C: grep FileSystemDefaultEncoding
 - make sure that mixing bytes and str is rejected

Added file: http://bugs.python.org/file11658/python3_bytes_filename.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3999] Real segmentation fault handler

[STINNER Victor]

New submission from STINNER Victor <[EMAIL PROTECTED]>:

I would like to be able to catch SIGSEGV in my Python code! So I 
started to hack Python trunk to support this feature. The idea is to 
use a signal handler which call longjmp(), and add setjmp() at 
Py_EvalFrameEx() enter.

See attached ("small") patch: segfault.patch

Example read.py with the *evil* ctypes module of invalid memory read:
--- 8< --
from ctypes import string_at

def fault():
text = string_at(1, 10)
print("text = {0!r}".format(text))

def test():
print("test: 1")
try:
fault()
except MemoryError, err:
print "ooops!"
print err

print("test: 2")
try:
fault()
except MemoryError, err:
print "ooops!"
print err

print("test: end")

def main():
test()

if __name__ == "__main__":
main()
--- 8< --

Result:
--- 8< --
$ python read.py
test: 1
sizeof()=160
ooops!
segmentation fault
test: 2
sizeof()=160
ooops!
segmentation fault
test: end
--- 8< --

Example bug1.py of a stack overflow:
--
loop = None,
for i in xrange(10**5):
loop = loop, None
--

Result:
--
$ python -i bug1.py

(...Traceback (most recent call last):
  File "", line 1, in 
MemoryError: segmentation fault

--

Python is able to restore a valid state (stack/heap) after a 
segmentation fault and raise a classical Python exception (I choosed 
MemoryError, but it could be a specific exception).

On my computer (Ubuntu Gutsy/i386), each segfault_frame takes 
sizeof(sigjmpbuf) + sizeof(void*) = 160 bytes, allocated on the stack. 
I don't know if it's huge or not, but that will limit the number of 
recursive calls. The feature can be optional if we add a configure 
option and some #ifdef/#endif. A dedicated stack is needed to be call 
the signal handler on stack overflow error. I choosed 4 KB, but since 
I only call longjmp(), smaller stack might also works.

Does other VM support such feature? JVM, Mono, .NET, etc. ?

I had the idea of catching SIGSEGV after reading the issue 1069092 
(stack overflow because of too many recursive calls).

--
files: segfault.patch
keywords: patch
messages: 74060
nosy: haypo
severity: normal
status: open
title: Real segmentation fault handler
Added file: http://bugs.python.org/file11659/segfault.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3894] imageop issue

[Benjamin Peterson]

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

Fixed in r66689 and r66690.

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

[issue3998] List.sort docstring has obsolete cmp reference.

[Benjamin Peterson]

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

Thanks. Fixed in r66692.

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

[issue3998] List.sort docstring has obsolete cmp reference.

[Benjamin Peterson]

Changes by Benjamin Peterson <[EMAIL PROTECTED]>:


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

[issue3988] Byte warning mode and b'' != ''

[Brett Cannon]

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

Setting as a deferred blocker since this is a 3.0 thing and not a 2.6 thing.

--
nosy: +brett.cannon
priority: release blocker -> deferred blocker

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3977] Check PyInt_AsSsize_t/PyLong_AsSsize_t error

[Benjamin Peterson]

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

Thanks for the patches. Fixed in r66693, r66694, and r66695.

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

[issue4000] Additional 2to3 documentation updates

[David W. Lambert]

New submission from David W. Lambert <[EMAIL PROTECTED]>:

http://docs.python.org/dev/3.0/howto/functional.html

a) Refers to "print statement" in Introduction,

b) Uses syntax no longer valid:

   def get_state ((city, state)):
   '''
   alas and unfortunately argument grouping
   is no longer permitted
   '''
   return state


Thanks, that's all for tonight.

--
assignee: georg.brandl
components: Documentation
messages: 74065
nosy: LambertDW, georg.brandl
severity: normal
status: open
title: Additional 2to3 documentation updates
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

[issue4000] Additional 2to3 documentation updates

[David W. Lambert]

Changes by David W. Lambert <[EMAIL PROTECTED]>:


___
Python tracker <[EMAIL PROTECTED]>

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