Changes by STINNER Victor :
--
nosy: +amaury.forgeotdarc, pitrou
___
Python tracker
<http://bugs.python.org/issue10763>
___
___
Python-bugs-list mailing list
Unsub
STINNER Victor added the comment:
I tested the patch version 11 on Windows: all tests pass. But #include
should be skipped on Windows (Python/fault.c): I will add #ifdef
MS_WINDOWS.
--
___
Python tracker
<http://bugs.python.org/issue8
STINNER Victor added the comment:
> I tested the patch version 11 on Windows: all tests pass.
Oh, and I forgot to say that the Windows fault handler does catch the fault too
(Windows opens a popup with a question like "Should the error be reported to
M
STINNER Victor added the comment:
Tested on FreeBSD 8: all tests pass (all of the 4 signals are supported) and
FreeBSD dumps a core file.
--
___
Python tracker
<http://bugs.python.org/issue8
STINNER Victor added the comment:
Tested on Ubuntu 10.04: all tests pass and apport intercepts the fault. Apport
ignores the faults because I am testing a Python executable compiled from SVN
(py3k). Apport logs (/var/log/apport.log):
---
apport (pid 18148) Thu Dec 23 13:29:25 2010: called for
STINNER Victor added the comment:
p3k_i9313.diff is just a workaround, not the correct fix. The problem is that
PyTokenizer_FindEncoding() doesn't get the filename.
I wrote tokenizer_encoding_filename.patch which add
PyTokenizer_FindEncodingFilename() and patch import.c and traceback
STINNER Victor added the comment:
See also #9738 (Document the encoding of functions bytes arguments of the C
API) to check which encoding is expected :-p
--
___
Python tracker
<http://bugs.python.org/issue9
STINNER Victor added the comment:
Georg rejected this patch in Python 3.2:
"I did say I like the feature, but that was a) before beta 2
was released, now the next release is a release candidate, and b) this
thread showed that it is not at all obvious how the feature should look
like. The
STINNER Victor added the comment:
Le vendredi 24 décembre 2010 à 14:46 +, Baptiste Carvello a écrit :
> the patch solves the bug for me as well (using locale "C", the
> filesystem encoding is utf-8). However, I do not understand why the
> patch checks that the sheban
STINNER Victor added the comment:
Update copy_script patch: add comments to explain why the shebang have to be
decodable from UTF-8 and from the script encoding.
--
Added file: http://bugs.python.org/file20165/copy_script-2.patch
___
Python tracker
STINNER Victor added the comment:
Fixed by r87485 (Python 3.2).
I don't want to fix it in 2.7 or 3.1, because maybe someone relies on this bug
and it's a minor bug :-) Reopen the issue if you would like a backport.
--
resolution: -> fixed
status: o
STINNER Victor added the comment:
Le samedi 25 décembre 2010 à 22:35 +, Éric Araujo a écrit :
> Victor: Your patch uses os.fsencode, so porting to distutils2 won’t be
> easy.
In Python 3.1, you can replace name=os.fsencode(name) by
name=name.encode(sys.getfilesystemen
STINNER Victor added the comment:
r87504 documents encodings of error functions.
r87505 documents encodings of unicode functions.
r87506 documents encodings of AST, compiler, parser and PyRun functions.
--
___
Python tracker
<http://bugs.python.
New submission from STINNER Victor :
decoding_fgets() decodes the input filename from UTF-8 whereas the filename is
encoded to the filesystem encoding. PyUnicode_DecodeFSDefault() should be used.
decoding_fgets() raises a SyntaxError("Non-UTF-8 code starting with '\xHH' in
f
New submission from STINNER Victor :
PyErr_WarnExplicit() expects a filename encoded to UTF-8. This function is only
called twice in the Python interpreter: compiler_assert() (with "assertion is
always true, perhaps remove parentheses?") and symtable_warn() (eg. with "name
&#
STINNER Victor added the comment:
See also issue #10779 (Change filename encoding to FS encoding in
PyErr_WarnExplicit()).
--
___
Python tracker
<http://bugs.python.org/issue10
STINNER Victor added the comment:
While documenting encodings, I found two issues: #10778 and #10779.
--
___
Python tracker
<http://bugs.python.org/issue9
New submission from STINNER Victor :
PyErr_SetFromWindowsErrWithFilename() expects a filename encoded to UTF-8. It
is called by win32_error() function of the nt (posix) module, and win32_error()
is called on an error in the bytes implementation of a function (if the
argument is a byte string
STINNER Victor added the comment:
issue10780.patch fixes this issue.
--
keywords: +patch
Added file: http://bugs.python.org/file20171/issue10780.patch
___
Python tracker
<http://bugs.python.org/issue10
STINNER Victor added the comment:
issue10780_mbcs_ignore.patch is a safer but more complex fix: use mbcs decoder
with the ignore error handler. Even if issue10780.patch might raise a
UnicodeDecodeError, I prefer it because it's shorter, simpler and so easier to
maintain the
STINNER Victor added the comment:
Oh, ignore "indenterror() (inconsistent use of tabs and spaces in indentation)
and", I forgot to remove it. indenterror() is correct.
--
___
Python tracker
<http://bugs.python.o
STINNER Victor added the comment:
https://github.com/haypo/faulthandler/wiki can be tried on this buildbot to get
more information about this issue. But the module have to be installed on this
host.
--
___
Python tracker
<http://bugs.python.
STINNER Victor added the comment:
Fixed by r87517.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue10779>
___
__
STINNER Victor added the comment:
Fixed by r87518.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue10778>
___
__
STINNER Victor added the comment:
Fixed by r87519.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue10780>
___
__
STINNER Victor added the comment:
This "feature" was introduced in a big commit from Guido van Rossum (made
before Python 3.0): r55500. The changelog is strange because it starts with
"Make test_zipfile pass. The zipfile module now does all I/O in binary mode
using bytes."
Changes by STINNER Victor :
--
resolution: invalid ->
status: closed -> open
___
Python tracker
<http://bugs.python.org/issue10783>
___
___
Python-bugs-
New submission from STINNER Victor :
The Python parser stores the filename as a byte string. But it decodes the
filename on error because most Python functions now use unicode strings.
Instead of decoding the filename at error, which may raise a new error, I
propose to decode the filename on
Changes by STINNER Victor :
Removed file: http://bugs.python.org/file20179/parse_filename_obj.patch
___
Python tracker
<http://bugs.python.org/issue10785>
___
___
Pytho
Changes by STINNER Victor :
Added file: http://bugs.python.org/file20180/parser_filename_obj.patch
___
Python tracker
<http://bugs.python.org/issue10785>
___
___
Pytho
STINNER Victor added the comment:
Issue #10785 prepares the work for this issue: store input filename as a
unicode string, instead of a byte string, in the parser.
--
___
Python tracker
<http://bugs.python.org/issue3
Changes by STINNER Victor :
--
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue3080>
___
___
Python-bugs-list mailing list
Unsub
STINNER Victor added the comment:
Amaury> At this point a feature change seems unlikely,
Amaury> but it's not too late to emit a DeprecationWarning.
I prefer to break the API today than having to maintain a broken API for
10 or 20 years :-) And we have a very small user base usi
STINNER Victor added the comment:
Fixed by r87537. Thanks Amaury for your review!
I also removed some ugly (implicit) conversions from test_struct.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.p
STINNER Victor added the comment:
Informations about SysV semaphores:
- functions: semget(), semop(), semctl(), ftok()
- http://perldoc.perl.org/IPC/SysV.html
- http://beej.us/guide/bgipc/output/html/multipage/semaphores.html
--
___
Python
STINNER Victor added the comment:
Examples of programs using SysV semaphores:
http://firebird.cvs.sourceforge.net/viewvc/firebird/firebird2/src/jrd/isc_sync.cpp?revision=HEAD&view=markup
(Firebird, search "#ifdef USE_SYS5SEMAPHORE" sections)
https://github.com/mono/mono/blob/
STINNER Victor added the comment:
> maybe a more elegant solution than changing the type conditional
> on PGEN can be found
In pgen, the filename is only used to display the following warning, in
indenterror():
: inconsistent use of tabs and spaces in indentation
In pratical
STINNER Victor added the comment:
When testing my patch, I found and fixed two bugs in pgen:
- r87557: PGEN was not defined to compile pgenmain.c and printgrammar.c
- r87558: pgen error was ignored on "make Parser/pgen.stamp" (when executing
pgen to compile t
STINNER Victor added the comment:
Version 2 of the patch:
- remove filename attribute from perrdetail and tok_state structure in PGEN
mode, and add a comment to explain why
- rename filename_obj to filename
- indenterror() no longer print the input filename in PGEN mode
--
Added
Changes by STINNER Victor :
--
nosy: +haypo
___
Python tracker
<http://bugs.python.org/issue5672>
___
___
Python-bugs-list mailing list
Unsubscribe:
STINNER Victor added the comment:
See also #5725.
--
___
Python tracker
<http://bugs.python.org/issue10348>
___
___
Python-bugs-list mailing list
Unsubscribe:
STINNER Victor added the comment:
See also http://semanchuk.com/philip/sysv_ipc/: "System V IPC for Python -
Semaphores, Shared Memory and Message Queues"
--
___
Python tracker
<http://bugs.python.o
STINNER Victor added the comment:
Le mercredi 29 décembre 2010 à 19:26 +, Alexander Belopolsky a
écrit :
> Would it look as exotic if presented like this?
>
> File "", line 1
> 𐌀 = 5
>^
> SyntaxError: invalid character in identifier
> (works
STINNER Victor added the comment:
> Unicode objects are NUL-terminated, but only very external APIs
> rely on this (e.g. code using the Windows Unicode API).
All Py_UNICODE_str*() functions rely on the NUL character. They are useful when
patching a function from bytes (char*) to u
STINNER Victor added the comment:
More info about FreeBSD.
"sysctl p1003_1b.sem_nsems_max" gives the maximum number of POSIX semaphores
(per process? system wide?).
Since FreeBSD 8.1, "sudo sysctl -w p1003_1b.sem_nsems_max=256" can be used to
change this limit at runt
STINNER Victor added the comment:
NetBSD.
Extract of the sem_close() manpage
http://www.daemon-systems.org/man/sem_close.3.html
---
STANDARDS
The sem_open(), sem_close(), and sem_unlink() functions conform to
ISO/IEC 9945-1:1996 (``POSIX.1'').
HISTORY
Support
STINNER Victor added the comment:
Darwin (Mac OS X).
According to the following email (July 2010), Darwin supports POSIX semaphores
and the default limit is 10,000 semaphores.
http://osdir.com/ml/darwin-dev/2010-07/msg00012.html
The limit is configurable via sysctl as kern.posix.sem.max
STINNER Victor added the comment:
OpenBSD.
According to Martin, OpenBSD doesn't implement POSIX semaphores.
---
I don't have an installation of OpenBSD, but...
In FreeBSD, POSIX semaphores are implemented in sys/kern/uipc_sem.c.
In
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/k
STINNER Victor added the comment:
base64, bz2, hex, quopri, rot13, uu and zlib codecs (reintroduced recently by
r86934, issue #7475) cannot be used by str.encode/bytes.decode, but with
.transform() and .untransform() methods of bytes and str objects. But these
methods were removed by r87176
STINNER Victor added the comment:
See issue #10807: 'base64' can be used with bytes.decode() (and str.encode()),
but it raises a confusing exception (TypeError: expected bytes, not memoryview).
--
___
Python tracker
<http://bu
Changes by STINNER Victor :
--
nosy: +georg.brandl
priority: normal -> release blocker
___
Python tracker
<http://bugs.python.org/issue10807>
___
___
Python-
STINNER Victor added the comment:
issue10807.patch just disables hex, base64, ... codecs in aliases (so it's
still possible to use they through codecs.lookup()).
--
keywords: +patch
Added file: http://bugs.python.org/file20224/issue10780.
Changes by STINNER Victor :
Removed file: http://bugs.python.org/file20224/issue10780.patch
___
Python tracker
<http://bugs.python.org/issue10807>
___
___
Python-bug
STINNER Victor added the comment:
Ah yes :-)
--
Added file: http://bugs.python.org/file20225/issue10807.patch
___
Python tracker
<http://bugs.python.org/issue10
STINNER Victor added the comment:
> Looks good, please commit.
Ok, done: r87642
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.or
STINNER Victor added the comment:
See also #6610 which has a patch with another test.
--
nosy: +haypo
___
Python tracker
<http://bugs.python.org/issue10
STINNER Victor added the comment:
> Sasha, commit is not working.
I suppose that the fix for the segfault is correct. The problem on Linux is the
new test: asc
>>> import time; time.asctime((12345, 1, 0, 0, 0, 0, 0, 0, 0))
'Mon Jan 1 00:00:00 12345\n'
asctime() of the
STINNER Victor added the comment:
Martin fixed test_concurrent_futures (#10798), this issue can be implemented
later.
--
type: -> feature request
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/issu
STINNER Victor added the comment:
> http://docs.python.org/library/time.html#time-y2kissues
> "Values 100–1899 are always illegal."
Why are these values illegal? The GNU libc accepts year in [1900-2^31; 2^31-1]
(tm_year in [-2147483648; 2147481747]). If time.accept2dyear=Fals
STINNER Victor added the comment:
Regression introduced by r87648 (issue #8013).
--
nosy: +haypo
___
Python tracker
<http://bugs.python.org/issue10814>
___
___
STINNER Victor added the comment:
test_time fails with an (C) assertion error on Windows: see issue #10814.
--
___
Python tracker
<http://bugs.python.org/issue8
STINNER Victor added the comment:
* r87680 fixes test_sockserver
* r87681 fixes test_timeout
* r87682 fixes test_tk
* r87683 fixes test_xmlrpc
* r87684 fixes test_socket
r87682, r87683, r87684 are patches from Nadeem Vawda.
On my Linux box, I am unable to get the warning on test_cgi or
STINNER Victor added the comment:
This issue is fixed in Python 3.2 beta 2:
$ ./python
>>> f=open("/dev/full", "wb")
>>> f.write(b'x')
1
>>> f.close()
IOError: [Errno 28] No space left on device
>>> ^D
sys:1: Resource
New submission from STINNER Victor :
test_remote (__main__.WithManagerTestRemoteManager) ...
/home/haypo/prog/GIT/py3k/Lib/multiprocessing/managers.py:812: ResourceWarning:
unclosed
util.debug('... decref failed %s', e)
ok
test_pool_initializer (__main__.TestInitializers) ...
/
STINNER Victor added the comment:
Ok, I found it: fixed by r87686
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
New submission from STINNER Victor :
The pydoc module has two DocHandler classes and two DocServer classes. I think
that they can be easily factorized.
DocServer may also use serve_forever()+shutdown() instead of
serve_until_quit()+quit flag, to be able to wait the server (with shutdown
STINNER Victor added the comment:
I opened this issue because I had to fix a bug twice in pydoc: r87687 (fix a
ResourceWarning(unclosed socket)).
--
___
Python tracker
<http://bugs.python.org/issue10
STINNER Victor added the comment:
* r87686 fixes multiprocessing
* r87687 fixes pydoc
* r87688 fixes test_subprocess
Remaining ResourceWarning warnings:
* test_imaplib
* test_urllibnet
* test_urllib2net
--
___
Python tracker
<h
STINNER Victor added the comment:
test_multiprocessing is still failing with "OSError: [Errno 23] Too many open
files in system" on "x86 FreeBSD 7.2 3.x":
http://www.python.org/dev/buildbot/builders/x86%20FreeBSD%207.2%203.x/builds/1396/steps/test/logs/stdio
I don'
New submission from STINNER Victor :
The following code raise a ValueError('I/O operation on closed file.'):
---
import socket
socket.socket(socket.SOCK_STREAM, socket.AF_INET)
s=socket.socket(socket.SOCK_STREAM, socket.AF_INET)
f=s.makefile("rb")
f.close()
print(repr(f))
--
Changes by STINNER Victor :
--
keywords: +patch
Added file: http://bugs.python.org/file20247/issue10819.patch
___
Python tracker
<http://bugs.python.org/issue10
STINNER Victor added the comment:
DeprecationWarnings:
* test_unittest: fixed by r87717
* test_array: fixed by r87719
* test_httplib: fixed by r87720
--
___
Python tracker
<http://bugs.python.org/issue10
STINNER Victor added the comment:
Antoine suggested me to patch SocketIO.name property instead of the
BufferedReader.__repr__() method: socketio_name.patch implements this idea.
--
Added file: http://bugs.python.org/file20248/socketio_name.patch
STINNER Victor added the comment:
As asked by Antoine, I commited my patch: r87722.
... But I don't know if it fixes the issue or not, I don't have access to a
Windows with more than 4 GB of memory.
--
___
Python tracker
<http://bu
STINNER Victor added the comment:
r87722 should fix the issue, but I didn't tested the fix... see #9611 for more
information.
--
nosy: +haypo
___
Python tracker
<http://bugs.python.org/i
STINNER Victor added the comment:
Fixed by r87728.
Wait for the buildbots before backporting to other versions.
--
___
Python tracker
<http://bugs.python.org/issue8
STINNER Victor added the comment:
Fixed by r87729.
Wait for the buildbots before backporting to other versions.
--
___
Python tracker
<http://bugs.python.org/issue8
STINNER Victor added the comment:
Fixed by r87730.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue10819>
___
__
STINNER Victor added the comment:
err_clear() should set err->filename to NULL.
--
versions: -Python 3.2
___
Python tracker
<http://bugs.python.org/issu
STINNER Victor added the comment:
Fixed by r87732
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue8992>
___
__
STINNER Victor added the comment:
(and by r87731)
--
___
Python tracker
<http://bugs.python.org/issue8992>
___
___
Python-bugs-list mailing list
Unsubscribe:
STINNER Victor added the comment:
> That may be what you meant, but "installed on this host" made me think
> I could do something external on the buildbot which I don't
> think would work given that the module has to be called from within
> the tests themselves?
If
New submission from STINNER Victor :
On "AMD64 Windows Server 2008 3.x", there are many "conversion from
'Py_ssize_t' to 'int', possible loss of data" errors:
Python\Python-ast.c(3403) : warning C4244: 'function' : conversion from
'Py
STINNER Victor added the comment:
r87733 fixes some conversions in:
* Python/pythonrun.c
* Objects/codeobject.c
* Objects/typeobject.c
* Objects/listobject.c
* Modules/_ctypes/_ctypes.c
* Modules/sha512module.c
* Modules/unicodedata.c
* Modules/selectmodule.c
* Modules/pyexpat.c
STINNER Victor added the comment:
r87734 fixes stdprinter.write().
--
___
Python tracker
<http://bugs.python.org/issue9611>
___
___
Python-bugs-list mailin
STINNER Victor added the comment:
#10823 has been marked as a duplicate of this issue.
--
___
Python tracker
<http://bugs.python.org/issue9566>
___
___
Python-bug
STINNER Victor added the comment:
amaury> r87733 in pyexpat.c modified a call to PyErr_Format with a %zi
amaury> format code. This format does not seem to be supported. %zd
amaury> should be used instead.
Oh, that's surprising. Why %zd is supported but not %zi?
PyUnico
STINNER Victor added the comment:
> Python\pystrtod.c(902) : 'function' : conversion from 'Py_ssize_t' to 'int',
> possible loss of data
> Python\pystrtod.c(1023) : '=' : conversion from 'Py_ssize_t' to 'int',
> possi
STINNER Victor added the comment:
I think that this issue is a duplicate of #8611 (and #9425), it should be fixed
in Python 3.2.
--
___
Python tracker
<http://bugs.python.org/issue10
STINNER Victor added the comment:
> But the comment is actually wrong: It says
>
> len <= buf_size <= INT_MAX (see above)
>
> however, len > buf_size may happen, after this code:
>
> if (len > buf_size) {
> PyErr_Format(PyExc_ValueError,
>
New submission from STINNER Victor :
Steps 1 and 3 of PyUnicode_FromFormatV() doesn't handle the format string "%%"
correctly. The loop responsible to skip the precision moves outside the format
string, and the function will then read uninitialized memory. The loop:
STINNER Victor added the comment:
pyexpat.patch: new try, does it look better?
--
keywords: +patch
Added file: http://bugs.python.org/file20263/pyexpat.patch
___
Python tracker
<http://bugs.python.org/issue9
STINNER Victor added the comment:
Oh, my first patch was wrong: it failed on %c format (in zipimport with
"%U%c%U"). The second version of the patch should be better.
--
Added file: http://bugs.python.org/file20264/pyunicode_fromforma
New submission from STINNER Victor :
PyUnicode_FromFormatV("%c") supposes that an unicode character is always stored
as a single Py_UNICODE word: but that's wrong on narrow build with characters
in [U+1; U+10].
Attached patch fixes this bug.
See also #10829.
--
New submission from STINNER Victor :
PyUnicode_FromFormatV() supports %d, %ld, %lld, %zd, %u, %lu, %llu, %zu, %i.
But it doesn't support %li, %lli, %zi.
Attached patch implements the 3 missing formats, and add unit tests for all
these formats.
--
components: Interpreter Core, Un
Changes by STINNER Victor :
--
nosy: +amaury.forgeotdarc
___
Python tracker
<http://bugs.python.org/issue10831>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by STINNER Victor :
--
nosy: +pitrou
___
Python tracker
<http://bugs.python.org/issue4953>
___
___
Python-bugs-list mailing list
Unsubscribe:
STINNER Victor added the comment:
PyBytes_FromFormatV() has the same issue.
--
___
Python tracker
<http://bugs.python.org/issue10829>
___
___
Python-bugs-list m
New submission from STINNER Victor :
It would be very practical use have a format, eg. '%y', to accept bytes object
in PyBytes_FromFormatV().
Example (extracted from posixmodule.c):
k = PyBytes_AsString(key2);
v = PyBytes_AsString(val2);
len = PyBytes_GET
New submission from STINNER Victor :
Guido created the "convenience function" PyErr_Format() 13 years ago (r7580)
with a naive implementation using char buffer[500] and vsprintf(). He added a
comment:
/* Caller is responsible for limiting the format */
Ok, that was true 13 year
3301 - 3400 of 35284 matches
Mail list logo
