[ python-Bugs-1120777 ] bug in unichr() documentation
Bugs item #1120777, was opened at 2005-02-11 13:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120777&group_id=5470 Category: Documentation Group: None Status: Open Resolution: None Priority: 5 Submitted By: Marko Kreen (mkz) Assigned to: Nobody/Anonymous (nobody) Summary: bug in unichr() documentation Initial Comment: http://www.python.org/doc/2.4/lib/built-in-funcs.html: > Return the Unicode string of one character whose Unicode > code is the integer i. > [...] > The argument must be in the range [0..65535], inclusive. unichr.__doc_ says: > Return a Unicode string of one character with ordinal i; 0 <= i <= 0x10. Which is correct? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120777&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1120777 ] bug in unichr() documentation
Bugs item #1120777, was opened at 2005-02-11 14:54 Message generated for change (Comment added) made by lemburg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120777&group_id=5470 Category: Documentation Group: None Status: Open Resolution: None Priority: 5 Submitted By: Marko Kreen (mkz) Assigned to: Nobody/Anonymous (nobody) Summary: bug in unichr() documentation Initial Comment: http://www.python.org/doc/2.4/lib/built-in-funcs.html: > Return the Unicode string of one character whose Unicode > code is the integer i. > [...] > The argument must be in the range [0..65535], inclusive. unichr.__doc_ says: > Return a Unicode string of one character with ordinal i; 0 <= i <= 0x10. Which is correct? -- >Comment By: M.-A. Lemburg (lemburg) Date: 2005-02-11 15:03 Message: Logged In: YES user_id=38388 Whether unichr() handles the UCS2 or the UCS4 range depends on the configuration option you set at Python compile time. Perhaps we should extend the documentation to mention this difference ?! Doc patches are welcome :-) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120777&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1120777 ] bug in unichr() documentation
Bugs item #1120777, was opened at 2005-02-11 13:54 Message generated for change (Comment added) made by mkz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120777&group_id=5470 Category: Documentation Group: None Status: Open Resolution: None Priority: 5 Submitted By: Marko Kreen (mkz) Assigned to: Nobody/Anonymous (nobody) Summary: bug in unichr() documentation Initial Comment: http://www.python.org/doc/2.4/lib/built-in-funcs.html: > Return the Unicode string of one character whose Unicode > code is the integer i. > [...] > The argument must be in the range [0..65535], inclusive. unichr.__doc_ says: > Return a Unicode string of one character with ordinal i; 0 <= i <= 0x10. Which is correct? -- >Comment By: Marko Kreen (mkz) Date: 2005-02-11 14:38 Message: Logged In: YES user_id=894541 Main problem for me was that the 65535 hints that unichr() may want UTF-16 values not Unicode. That was rather confusing. Ok, attached path clarifies unichr() range. -- Comment By: M.-A. Lemburg (lemburg) Date: 2005-02-11 14:03 Message: Logged In: YES user_id=38388 Whether unichr() handles the UCS2 or the UCS4 range depends on the configuration option you set at Python compile time. Perhaps we should extend the documentation to mention this difference ?! Doc patches are welcome :-) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120777&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1120452 ] Python 2.4.0 crashes with a segfault, EXAMPLE ATTACHED
Bugs item #1120452, was opened at 2005-02-11 00:04 Message generated for change (Comment added) made by mwh You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120452&group_id=5470 Category: Python Interpreter Core Group: Python 2.4 Status: Open Resolution: None Priority: 5 Submitted By: Viktor Ferenczi (complex) Assigned to: Nobody/Anonymous (nobody) Summary: Python 2.4.0 crashes with a segfault, EXAMPLE ATTACHED Initial Comment: Running the attached example crashes python 2.4.0 on linux (segfault) and Windows. Python is compiled on Debian Linux 3.0r3 (Woody). On Windows XP, I used the MSI installer downloaded from python.org This may be a problem with the regular expression module, but I'm not sure. Please assign a new category if it appears as a regexp bug. This bug causes permanent crashes in my new WEB applications. Old apps not using regexp and PyMeld seem to run correctly. Thanks for 2.4.1. -- >Comment By: Michael Hudson (mwh) Date: 2005-02-11 14:57 Message: Logged In: YES user_id=6656 What do you do to make it crash? "python index.py"? It doesn't fail for me with CVS HEAD. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120452&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1120862 ] Problem in join function definition
Bugs item #1120862, was opened at 2005-02-11 15:43 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120862&group_id=5470 Category: Documentation Group: Python 2.5 Status: Open Resolution: None Priority: 5 Submitted By: yseb (yseb) Assigned to: Nobody/Anonymous (nobody) Summary: Problem in join function definition Initial Comment: There is a problem in the last sentence of the join definition. == join( words[, sep]) Concatenate a list or tuple of words with intervening occurrences of sep. The default value for sep is a single space character. It is always true that "string.join (string.split(s, sep), sep)" equals s. == It is true that string.join(string.split(s, sep), sep)" is always equals to s. But string.join(string.split(s)) is not always equals to s especially for repeated sequence of spaces. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120862&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-919614 ] Python configured with --disable-unicode fails tests, more
Bugs item #919614, was opened at 2004-03-19 11:23
Message generated for change (Comment added) made by fdrake
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=919614&group_id=5470
Category: Installation
>Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Fred L. Drake, Jr. (fdrake)
Assigned to: Nobody/Anonymous (nobody)
Summary: Python configured with --disable-unicode fails tests, more
Initial Comment:
When building Python with:
./configure --disable-unicode
the test suite has many spurious failures because
modules and tests assume that unicode support is available.
Installing this Python (using "make install") fails at
the end of the first run of compileall.py, since that
script detects and reports failures; the output
contains many lines with the message
Sorry: ValueError: ('Unicode escapes not legal when
Unicode disabled',)
This should be fixed, or --disable-unicode should be
removed.
--
>Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2005-02-11 12:23
Message:
Logged In: YES
user_id=3066
The trunk and release24-maint branch will no longer compile
with --diable-unicode. I get the following error message
from the trunk:
c++ -pthread -Xlinker -export-dynamic -o python
Modules/python.o libpython2.5.a -lpthread -ldl -lutil -lm
libpython2.5.a(posixmodule.o)(.text+0x39a0): In function
`posix_tmpnam':
../Modules/posixmodule.c:6161: warning: the use of
`tmpnam_r' is dangerous, better use `mkstemp'
libpython2.5.a(posixmodule.o)(.text+0x3906): In function
`posix_tempnam':
../Modules/posixmodule.c:6116: warning: the use of `tempnam'
is dangerous, better use `mkstemp'
libpython2.5.a(_codecsmodule.o)(.text+0xf9): In function
`codec_encode':
../Modules/_codecsmodule.c:108: undefined reference to
`PyUnicode_GetDefaultEncoding'
libpython2.5.a(_codecsmodule.o)(.text+0x165): In function
`codec_decode':
../Modules/_codecsmodule.c:141: undefined reference to
`PyUnicode_GetDefaultEncoding'
collect2: ld returned 1 exit status
The release24-maint branch gives similar results.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=919614&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1115989 ] xmlrpclib: wrong decoding in '_stringify'
Bugs item #1115989, was opened at 2005-02-04 01:25
Message generated for change (Comment added) made by fdrake
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1115989&group_id=5470
Category: Python Library
Group: Python 2.3
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Dieter Maurer (dmaurer)
>Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: xmlrpclib: wrong decoding in '_stringify'
Initial Comment:
'_stringify' tries to convert a unicode string
into a pure ascii string by 'str(string)'.
This can lead to catastrophic behaviour when
Python's "defaultencoding" is not "ascii".
The attached patch uses "string.encode('ascii')"
instead
to become independent of the default encoding.
--
>Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2005-02-11 13:06
Message:
Logged In: YES
user_id=3066
Fixed for Python 2.4.1 and 2.5:
Lib/xmlrpclib.py 1.36.2.1, 1.40
Lib/test/test_xmlrpc.py 1.5.4.1, 1.7
I committed the attached patch and added a unit test.
Python 2.3 got left out since this doesn't seem critical
enough to destabilize old applications. I won't strongly
object if someone backports it to 2.3.6, if they actually
think there's going to be a 2.3.6.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1115989&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1120452 ] Python 2.4.0 crashes with a segfault, EXAMPLE ATTACHED
Bugs item #1120452, was opened at 2005-02-10 19:04
Message generated for change (Comment added) made by jimjjewett
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120452&group_id=5470
Category: Python Interpreter Core
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Viktor Ferenczi (complex)
Assigned to: Nobody/Anonymous (nobody)
Summary: Python 2.4.0 crashes with a segfault, EXAMPLE ATTACHED
Initial Comment:
Running the attached example crashes python 2.4.0 on linux (segfault) and
Windows. Python is compiled on Debian Linux 3.0r3 (Woody). On Windows XP, I
used the MSI installer downloaded from python.org
This may be a problem with the regular expression module, but I'm not sure.
Please assign a new category if it appears as a regexp bug.
This bug causes permanent crashes in my new WEB applications. Old apps not
using regexp and PyMeld seem to run correctly.
Thanks for 2.4.1.
--
Comment By: Jim Jewett (jimjjewett)
Date: 2005-02-11 14:36
Message:
Logged In: YES
user_id=764593
Partially reproduced on Windows XP. (Using the stock 2.4.
0 msi)
Just loading it in IDLE and hitting F5 (run), it prints None,
as though it had succeeded perfectly.
Typing in the commands from index.py by hand, I can get
it to give me the "encountered an error; Tell Microsoft?"
box, but IDLE only restarts instead of actually crashing.
There seems to a problem between the __getattr__ and
the __setattr__ in PyMeld.
"""
>>> p=Meld(open('player.html','rb').read())
>>> p.StreamURL1.value
'mss://stream.url'
>>> p.StreamURL2
>>> p.StreamURL2.src
'mms://stream.url'
>>> v=Video()
>>> v.stream
's'
>>> p.StreamURL1.value=v.stream
>>> p.StreamURL1.value
>>>
RESTART
>>>
"""
--
Comment By: Michael Hudson (mwh)
Date: 2005-02-11 09:57
Message:
Logged In: YES
user_id=6656
What do you do to make it crash? "python index.py"?
It doesn't fail for me with CVS HEAD.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120452&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1120452 ] Python 2.4.0 crashes with a segfault, EXAMPLE ATTACHED
Bugs item #1120452, was opened at 2005-02-10 19:04
Message generated for change (Comment added) made by jimjjewett
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120452&group_id=5470
Category: Python Interpreter Core
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Viktor Ferenczi (complex)
Assigned to: Nobody/Anonymous (nobody)
Summary: Python 2.4.0 crashes with a segfault, EXAMPLE ATTACHED
Initial Comment:
Running the attached example crashes python 2.4.0 on linux (segfault) and
Windows. Python is compiled on Debian Linux 3.0r3 (Woody). On Windows XP, I
used the MSI installer downloaded from python.org
This may be a problem with the regular expression module, but I'm not sure.
Please assign a new category if it appears as a regexp bug.
This bug causes permanent crashes in my new WEB applications. Old apps not
using regexp and PyMeld seem to run correctly.
Thanks for 2.4.1.
--
Comment By: Jim Jewett (jimjjewett)
Date: 2005-02-11 14:55
Message:
Logged In: YES
user_id=764593
__gettattr__ alone can provoke the crash, if used several
times, and on sub-melds.
I can print both StreamURL1 and StreamURL2.
If I ask it for p.StreamURL2.src and p.StreamURL1.value,
it prints whichever one I ask for first, and then crashes on
the second. I did get it to print both (not assign, just
__getattr__) by first getting several other attributes from
p.StreamURL1, including some that didn't exist, so that
there was a raise AttributeError in between. Doing this a
half dozen times, I provoked a MemoryError.
"""
>>> p.StreamURL1.value
'mss://stream.url'
>>> p.StreamURL2.src
Traceback (most recent call last):
File "", line 1, in -toplevel-
p.StreamURL2.src
File "C:\Python24\Lib\site-packages\segfault240\PyMeld.
py", line 475, in __getattr__
start = self._findElementFromID(name)
File "C:\Python24\Lib\site-packages\segfault240\PyMeld.
py", line 425, in _findElementFromID
match = _findIDMatch(nodeID, subset)
File "C:\Python24\Lib\site-packages\segfault240\PyMeld.
py", line 282, in _findIDMatch
match = re.search(thisRE, text)
File "C:\Python24\lib\sre.py", line 134, in search
return _compile(pattern, flags).search(string)
MemoryError
>>>
"""
--
Comment By: Jim Jewett (jimjjewett)
Date: 2005-02-11 14:36
Message:
Logged In: YES
user_id=764593
Partially reproduced on Windows XP. (Using the stock 2.4.
0 msi)
Just loading it in IDLE and hitting F5 (run), it prints None,
as though it had succeeded perfectly.
Typing in the commands from index.py by hand, I can get
it to give me the "encountered an error; Tell Microsoft?"
box, but IDLE only restarts instead of actually crashing.
There seems to a problem between the __getattr__ and
the __setattr__ in PyMeld.
"""
>>> p=Meld(open('player.html','rb').read())
>>> p.StreamURL1.value
'mss://stream.url'
>>> p.StreamURL2
>>> p.StreamURL2.src
'mms://stream.url'
>>> v=Video()
>>> v.stream
's'
>>> p.StreamURL1.value=v.stream
>>> p.StreamURL1.value
>>>
RESTART
>>>
"""
--
Comment By: Michael Hudson (mwh)
Date: 2005-02-11 09:57
Message:
Logged In: YES
user_id=6656
What do you do to make it crash? "python index.py"?
It doesn't fail for me with CVS HEAD.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1120452&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
