[issue3006] subprocess.Popen causes socket to remain open after close
Charles-Francois Natali neolo...@free.fr added the comment: I cannot figure out why the closesocket's graceful shutdown is waiting for the Popen command to complete. It doesn't. Your main process closes its socket. You could see it with a netstat/lsof (don't know under Windows). The problem is that when you call subprocess.Popen(), there's a fork behind, and the child process receives a copy of the FD. That's why your socket is not deallocated until the subprocess completes (and closes the FD on exit). This problem does not show up with the equivalent os.popen command. That's because os.popen() is implemented as subprocess.Popen with close_fds=True, so the socket is closed before execve is called. IMHO, setting close_fds=True by default is the Right Thing to do (and I think it's now done by default in py3k to avoid races between concurrent popen calls, in addition to setting pipe's FD as FD_CLOEXEC). -- nosy: +neologix ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3006 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9124] Mailbox module demonstrates infeasibly slow performance
Lennart Regebro rege...@gmail.com added the comment: I can confirm on Ubuntu and with other example mailboxes. Looping through the messages and printing the subjects takes around 200-300 times longer under Python 3 than under Python 2. -- nosy: +lregebro ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9124 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9124] Mailbox module demonstrates infeasibly slow performance
Changes by Raymond Hettinger rhettin...@users.sourceforge.net: -- priority: normal - high ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9124 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9124] Mailbox module demonstrates infeasibly slow performance
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: Can you confirm using the Py3.2 head? Am curious if Antoine's optimizations helped here. -- nosy: +pitrou, rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9124 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10441] some stdlib modules need to be updated to handle SSL certificate validation
Éric Araujo mer...@netwok.org added the comment: We tend to spend some time on documentation: http://docs.python.org/dev/library/ssl#ssl.SSLContext.set_default_verify_paths -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10441 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10441] some stdlib modules need to be updated to handle SSL certificate validation
david db.pub.m...@gmail.com added the comment: Cool yeah. The documentation is good I asked the question because I wasn't sure if it was in a pending patch elsewhere in the bug tracker or was accepted. I guess I should have googled for it. Thank you. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10441 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9124] Mailbox module demonstrates infeasibly slow performance
Lennart Regebro rege...@gmail.com added the comment: 3.2 sees a small improvement when running the Steve test: Python 2.6.6: 0.0291s Python 3.1.2: 31.1s Python 3.2b2+: 28.8s This is Ubuntu 10.04 on ext3, with all Pythons compiled from source, with no configure attributes except a prefix. I wonder if the differences between different unix systems can have to do with what the default system encoding is? Mine is UTF-8. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9124 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10891] Tweak sorting howto to eliminate redundancy
New submission from Éric Araujo mer...@netwok.org: When reading over the sorting howto, I noticed redundancy of the form “the list.sort() method of a list”. Raymond, if you approve the attached patch, please assign back to me. There were no warnings during doc build and no link was broken. Note that :meth:`list.sort` (or :meth:`~list.sort`) does not trigger a link to the doc of the method, since sort is not marked up with a method directive but listed in a table alongside other list and bytearray methods (http://docs.python.org/dev/library/stdtypes#typesseq-mutable). This table is preceded by index-generating markup, but it does not create a target for :meth:`list.sort`; that’s a separate issue. Until it’s solved, the sorting howto could turn the first occurrence of “list” into a link to the right section, using :ref:`typesseq-mutable list`, or continue to live without a link to list or list.sort. -- assignee: rhettinger components: Documentation files: minor-sorting-changes.diff keywords: patch messages: 126083 nosy: d...@python, eric.araujo, rhettinger priority: normal severity: normal stage: commit review status: open title: Tweak sorting howto to eliminate redundancy versions: Python 2.7, Python 3.1, Python 3.2 Added file: http://bugs.python.org/file20364/minor-sorting-changes.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10891 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8957] strptime(.., '%c') fails to parse output of strftime('%c', ..) in some locales
STINNER Victor victor.stin...@haypocalc.com added the comment:
On Linux, cfmt.py fails on fr_FR locale (the only valid locale in the list of
tested locales):
---
fr_FR [mer. 12 janv. 2011 11:30:35 CET] %a %d %B %Y %H:%M:%S %Z != %a %d %b %Y
%T %Z
---
The problem is the month format: locale.nl_langinfo(locale.D_T_FMT) returns '%a
%d %b %Y %T %Z', but _strptime (LocaleTime().LC_date_time) uses '%a %d %B %Y
%H:%M:%S %Z' = '%b' vs '%B'.
_strptime.LocalTime.__calc_date_time() uses strftime('%c') and then parse the
output to get the complete format. But it uses strftime('%c') with the march
month, and in french, march is formatted 'mars' for both month formats (%b
*and* %B).
_strptime.LocalTime.__calc_date_time() should detect that the month has the
same format with %b and %B, and try other timestamps (other months).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8957
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9124] Mailbox module should use binary I/O, not text I/O
Antoine Pitrou pit...@free.fr added the comment: The aforementioned python-dev thread (available at http://mail.python.org/pipermail/python-dev/2010-June/101186.html ) explains things quite well. The mailbox module needs to be modified to use binary I/O, both for functionality and for speed. Right now, I don't know how the mailbox module can be useful in py3k (you'd quickly run into unicode errors as soon as you try to read an email with another charset, I think). -- stage: unit test needed - needs patch title: Mailbox module demonstrates infeasibly slow performance - Mailbox module should use binary I/O, not text I/O type: performance - behavior versions: +Python 3.2, Python 3.3 -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9124 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10892] segfault with del X.__abstractmethods__
New submission from Amaury Forgeot d'Arc amaur...@gmail.com: A short crasher:: class X(object): pass del X.__abstractmethods__ All versions since 2.6 are affected. The fix is probably simple: the setter function type_set_abstractmethods() in typeobject.c should check for a NULL value. -- keywords: easy messages: 126086 nosy: amaury.forgeotdarc priority: critical severity: normal status: open title: segfault with del X.__abstractmethods__ type: crash versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10892 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10892] segfault with del X.__abstractmethods__
Éric Araujo mer...@netwok.org added the comment: I think a crash does not qualify as security issue, hence removing 2.6. -- nosy: +eric.araujo versions: -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10892 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue775321] plistlib error handling
Éric Araujo mer...@netwok.org added the comment: I think this was closed prematurely. I would like a core dev to assess this issue and reject or validate it. -- nosy: +eric.araujo -BreamoreBoy resolution: wont fix - stage: patch review - status: closed - open versions: +Python 3.3 -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue775321 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue775321] plistlib error handling
Changes by Éric Araujo mer...@netwok.org: -- nosy: +georg.brandl, mher, ned.deily, ronaldoussoren ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue775321 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue985064] plistlib crashes too easily on bad files
Éric Araujo mer...@netwok.org added the comment: See also reopened dependency #775321. -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue985064 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10893] The docs mark staticmethod as a function
New submission from Ram Rachum cool...@cool-rr.com: The Python documentation uses :func:`staticmethod` to describe staticmethod, while staticmethod is a type. I want to link to the Python documentation from my project's documentation using Intersphinx, and I wouldn't want to mislead my users by marking static method as a function. -- assignee: d...@python components: Documentation messages: 126090 nosy: cool-RR, d...@python priority: normal severity: normal status: open title: The docs mark staticmethod as a function type: behavior versions: Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10893 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode
STINNER Victor victor.stin...@haypocalc.com added the comment:
With gcc-4.6 -O1, Python 3.2 works correctly. With gcc-4.6 -O1
-ftree-vectorize, the assertion assert (new_line - last_line 255); fails in
PyCode_Optimize().
I think that the problem is in the following loop:
-
#define NOP9
#define HAVE_ARGUMENT 90 /* Opcodes from here have an argument: */
#define HAS_ARG(op) ((op) = HAVE_ARGUMENT)
#define CODESIZE(op) (HAS_ARG(op) ? 3 : 1)
unsigned char *codestr = NULL;
Py_ssize_t codelen;
int *addrmap = NULL;
/* Fixup linenotab */
for (i=0, nops=0 ; icodelen ; i += CODESIZE(codestr[i])) {
addrmap[i] = i - nops;
if (codestr[i] == NOP)
nops++;
}
-
gcc-4.6 -O1:
-
0x00480991 +5041: mov%eax,%edx
0x00480993 +5043: sub%esi,%edx
0x00480995 +5045: mov%edx,(%r12,%rax,4)
0x00480999 +5049: movzbl 0x0(%rbp,%rax,1),%edx
0x0048099e +5054: cmp$0x9,%dl
0x004809a1 +5057: jne0x4809a8 PyCode_Optimize+5064
0x004809a3 +5059: add$0x1,%esi
0x004809a6 +5062: jmp0x4809b2 PyCode_Optimize+5074
0x004809a8 +5064: mov$0x3,%ecx
0x004809ad +5069: cmp$0x59,%dl
0x004809b0 +5072: ja 0x4809b7 PyCode_Optimize+5079
0x004809b2 +5074: mov$0x1,%ecx
0x004809b7 +5079: add%rcx,%rax
0x004809ba +5082: cmp%rax,%rdi
0x004809bd +5085: jg 0x480991 PyCode_Optimize+5041
-
gcc-4.6 -O1 -ftree-vectorize
-
0x00480991 +5041: mov%eax,%ecx
0x00480993 +5043: sub%edx,%ecx
0x00480995 +5045: mov%ecx,(%r12,%rax,4)
0x00480999 +5049: movzbl 0x0(%rbp,%rax,1),%ecx
0x0048099e +5054: lea0x1(%rdx),%esi
0x004809a1 +5057: cmp$0x9,%cl
0x004809a4 +5060: cmovne %edx,%esi
0x004809a7 +5063: cmove %esi,%edx
0x004809aa +5066: setne %cl
0x004809ad +5069: movzbl %cl,%ecx
0x004809b0 +5072: lea0x1(%rax,%rcx,2),%rax
0x004809b5 +5077: cmp%rax,%rdi
0x004809b8 +5080: jg 0x480991 PyCode_Optimize+5041
-
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9880
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode
STINNER Victor victor.stin...@haypocalc.com added the comment: More info about the loop: Py_ssize_t i; int nops; My setup: * Intel(R) Pentium(R) 4 CPU 3.00GHz * Debian Sid * gcc (Debian 20110106-1) 4.6.0 20110106 (experimental) [trunk revision 168538] -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9880 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1488934] file.write + closed pipe = no error
Charles-Francois Natali neolo...@free.fr added the comment:
This is normal behaviour: stdout is normally line buffered (_IOLBF) only if
connected to a tty.
When it's not connected to a tty, it's full buffered (_IOFBF). This is done on
purpose for performance reason. To convince yourself, run
$ cat test.py
for i in range(1, 100):
print('hello world')
$ time python test.py /tmp/foo
With buffering off (-u option), the same commande takes almost 10 times longer.
If the application wants to be sure to receive a SIGPIPE when the pipe's end is
closed, it should just flush stdout explicitely (sys.stdout.flush()).
Suggesting to close.
--
nosy: +neologix, pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1488934
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10894] Making stdlib APIs private
New submission from SilentGhost ghost@gmail.com: Following suggestion in the Developers Guide (http://docs.python.org/devguide/#index-5) and the rules proposed by Michael Foord (http://mail.python.org/pipermail/python-dev/2010-November/105476.html): If a module or package defines __all__ that authoritatively defines the public interface. Modules with __all__ SHOULD still respect the naming conventions (leading underscore for private members) to avoid confusing users. Modules SHOULD NOT export private members in __all__. Names imported into a module a never considered part of its public API unless documented to be so or included in __all__. Methods / functions / classes and module attributes whose names begin with a leading underscore are private. If a class name begins with a leading underscore none of its members are public, whether or not they begin with a leading underscore. If a module name in a package begins with a leading underscore none of its members are public, whether or not they begin with a leading underscore. If a module or package doesn't define __all__ then all names that don't start with a leading underscore are public. All public members MUST be documented. Public functions, methods and classes SHOULD have docstrings. Private members may have docstrings. Where in the standard library this means that a module exports stuff that isn't helpful or shouldn't be part of the public API we need to migrate to private names and follow our deprecation process for the public names. The following deprecation method is adopted: from warnings import warn as _warn def no_underscore(parameters): _warn(The module.no_underscore() function is deprecated, DeprecationWarning, 2) return _no_underscore(parameters) Note: this is a meta-issue. It should only depend on all individual issues fixing APIs. It's currently dependant only on resolved issue10371. As I don't think it's reasonable to create an issue per stdlib module, I'm going to group a few modules in issue. However, when submitting patches, please create a patch per module to minimize disturbance. The files to check: Lib/module.py, Lib/test/test_module.py, Doc/library/module.rst -- components: Library (Lib) messages: 126094 nosy: SilentGhost, brett.cannon priority: normal severity: normal status: open title: Making stdlib APIs private versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10894 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10895] Private stdlib API: getopt, getpass, glob, gzip, genericpath, gettext
New submission from SilentGhost ghost@gmail.com: Module generic path is in order (added here only for completeness). Attached patch is for getopt. -- components: Library (Lib) files: getopt_api.diff keywords: patch messages: 126095 nosy: SilentGhost priority: normal severity: normal status: open title: Private stdlib API: getopt, getpass, glob, gzip, genericpath, gettext versions: Python 3.3 Added file: http://bugs.python.org/file20365/getopt_api.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10895 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10894] Making stdlib APIs private
SilentGhost ghost@gmail.com added the comment: Depends on issue10895 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10894 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode
Antoine Pitrou pit...@free.fr added the comment: [...] gcc-4.6 -O1 -ftree-vectorize - 0x00480991 +5041: mov%eax,%ecx 0x00480993 +5043: sub%edx,%ecx 0x00480995 +5045: mov%ecx,(%r12,%rax,4) 0x00480999 +5049: movzbl 0x0(%rbp,%rax,1),%ecx 0x0048099e +5054: lea0x1(%rdx),%esi 0x004809a1 +5057: cmp$0x9,%cl 0x004809a4 +5060: cmovne %edx,%esi 0x004809a7 +5063: cmove %esi,%edx 0x004809aa +5066: setne %cl 0x004809ad +5069: movzbl %cl,%ecx 0x004809b0 +5072: lea0x1(%rax,%rcx,2),%rax 0x004809b5 +5077: cmp%rax,%rdi 0x004809b8 +5080: jg 0x480991 PyCode_Optimize+5041 - Looks like code generation is borked. (it lacks a compare to 0x59 or 0x5a (90), and setne wouldn't be the right instruction anyway) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9880 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode
STINNER Victor victor.stin...@haypocalc.com added the comment: Looks like code generation is borked. I sent an email to the mailing list: http://gcc.gnu.org/ml/gcc-help/2011-01/msg00136.html -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9880 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10895] Private stdlib API: getopt, getpass, glob, gzip, genericpath, gettext
SilentGhost ghost@gmail.com added the comment: Attached patch is for glob. While I haven't touched it, I find it strange that Doc/library/glob.rst draws special attention to the actual source code of the glob module. Since, in my view, it's pertaining to the public API, I would consider deleting that See also note. -- Added file: http://bugs.python.org/file20366/glob_api.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10895 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10895] Private stdlib API: getopt, getpass, glob, gzip, genericpath, gettext
SilentGhost ghost@gmail.com added the comment: Attached patch is for getpass. Additionally, I let myself remove superfluous import. -- Added file: http://bugs.python.org/file20367/getpass_api.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10895 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10896] trace module compares directories as strings (--ignore-dir)
New submission from Vladimir Rutsky rutsky.vladi...@gmail.com: This is code from recent trace.py (http://svn.python.org/view/python/branches/release27-maint/Lib/trace.py?view=markup): trace.py:169: # Ignore a file when it contains one of the ignorable paths for d in self._dirs: # The '+ os.sep' is to ensure that d is a parent directory, # as compared to cases like: # d = /usr/local # filename = /usr/local.py # or # d = /usr/local.py # filename = /usr/local.py if filename.startswith(d + os.sep): self._ignore[modulename] = 1 return 1 Directories comparison like filename.startswith(d + os.sep) works incorrect on case-insensitive filesystems (such as NTFS on Windows). This leads to confusing results on Windows: python trace.py --ignore-dir='$prefix' -t test.py or python trace.py --ignore-dir C:\Python26\Lib -t test.py shows all calls from standard library, but this one doesn't: python trace.py --ignore-dir=c:\python26\lib -t test.py See attached test files and log for details. -- components: Library (Lib) files: test.py messages: 126101 nosy: vrutsky priority: normal severity: normal status: open title: trace module compares directories as strings (--ignore-dir) versions: Python 2.7 Added file: http://bugs.python.org/file20368/test.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10896 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10896] trace module compares directories as strings (--ignore-dir)
Changes by Vladimir Rutsky rutsky.vladi...@gmail.com: Added file: http://bugs.python.org/file20369/test.cmd ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10896 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10896] trace module compares directories as strings (--ignore-dir)
Changes by Vladimir Rutsky rutsky.vladi...@gmail.com: Added file: http://bugs.python.org/file20370/test.out ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10896 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10893] The docs mark staticmethod as a function
SilentGhost ghost@gmail.com added the comment: So, is int, str, bool and enumerate. And many others. The preface on functions page (http://docs.python.org/dev/library/functions.html) says: The Python interpreter has a number of functions and types built into it that are always available. I would think it's clear enough. -- nosy: +SilentGhost ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10893 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10895] Private stdlib API: getopt, getpass, glob, gzip, genericpath, gettext
SilentGhost ghost@gmail.com added the comment: Attached patch is for gzip. Additionally, I had to fix import and removed two unused (?) functions. Let me know if that's inappropriate. I wasn't sure what to do about constants (all caps vars) so I left them as they were. -- Added file: http://bugs.python.org/file20371/gzip_api.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10895 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10895] Private stdlib API: getopt, getpass, glob, gzip, genericpath, gettext
Changes by SilentGhost ghost@gmail.com: Removed file: http://bugs.python.org/file20367/getpass_api.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10895 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10895] Private stdlib API: getopt, getpass, glob, gzip, genericpath, gettext
Changes by SilentGhost ghost@gmail.com: Added file: http://bugs.python.org/file20372/getpass_api.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10895 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10897] UNIX mmap unnecessarily dup() file descriptor
New submission from Lorenz Huedepohl lor...@mpa-garching.mpg.de: The UNIX mmap version in Modules/mmapmodule.c makes a call to dup() to duplicate the file descriptor that is passed for creating the memory-mapped region. This way, I frequently hit the limit for the number of open file handles while creating mmap.mmap() instances, despite closing all my opened files after creating a mapping for them. My application is scientific data (read: large data :-) analysis for which mmap() is very well suited together with numpy/scipy - however, the large number of files causes me to hit the resource limit on open file handles) I propose to remove this dup(), which was apparently introduced in the process of fixing issue #728515, concerning incorrect behavior of the mmap.resize() method on UNIX, as it was feared the user could have closed the file handle already. I think it should be the responsibility of the user not to close the file in question or either - if it needs to be closed - not to call the resize method later. I should stress that a call to mmap(2) does not require an open file handle during the time of the mapping but that a duplicate of the file handle was only kept to allow .size() and .resize() to work. See the POSIX Programmer's Manual: The mmap() function shall add an extra reference to the file associated with the file descriptor fildes which is not removed by a subsequent close() on that file descriptor. This reference shall be removed when there are no more mappings to the file. It would be great if this little nicety would translate better to Python! Regards, Lorenz -- components: Library (Lib) files: no_dup.patch keywords: patch messages: 126104 nosy: lorenz priority: normal severity: normal status: open title: UNIX mmap unnecessarily dup() file descriptor type: resource usage versions: Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3 Added file: http://bugs.python.org/file20373/no_dup.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10897 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue775321] plistlib error handling
Mher Movsisyan mher.movsis...@gmail.com added the comment: I don't see compelling reasons to wrap ExpatError in ValueError. ExpatError contains extra diagnostic information such as line and column numbers. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue775321 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10855] wave.Wave_read.close() doesn't release file
Peter Creath pjcreath+pyt...@gmail.com added the comment: Thank you for clarifying the documentation. However, I don't think that fully resolves the issue. I'm not complaining about a failure to close the file. As you observe, it doesn't need to (and shouldn't) close a file object, but it should release the reference. The code already tries to release the reference (self._file = None). It just fails to release it correctly, missing the other reference to the file object (self._data_chunk). That's the bug. Your clarification of the documentation is appreciated nonetheless. I've attached a patch as Ned requested. The same patch can currently be applied to release27-maint, release31-maint, and py3k. (The line numbers and surrounding context are identical.) -- keywords: +patch resolution: fixed - status: closed - open versions: +Python 2.5, Python 2.6, Python 3.1 Added file: http://bugs.python.org/file20374/issue10855.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10855 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10225] Fix doctest runable examples in python manual
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: I have updated Sphinx and rerun py3k doctests. It looks like the newest Sphinx does not check examples unless the file has a .. testsetup:: directive somewhere. This is nice because it focuses on the files that are clearly intended to be doctest-checked. Of course, there are many perfectly good code examples that are now skipped, but this can be addressed in the next step. I am attaching a patch that makes the following command succeed in py3k Doc directory: $ sphinx-build --version Sphinx v1.1pre .. $ sphinx-build -b doctest -d build/doctrees . build/doctest .. Doctest summary === 581 tests 0 failures .. Most of the changes in issue10225-py3k.diff are non-controvercial with the exception of code fixes in collections and difflib. In collections, I removed trailing whitespace from generated namedtuple code and in difflib I changed get_close_matches() return value from map object to a list. I would appreciate comments on these two changes. -- Added file: http://bugs.python.org/file20375/issue10225-py3k.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10892] segfault with del X.__abstractmethods__
Benjamin Peterson benja...@python.org added the comment: r87954 -- nosy: +benjamin.peterson resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10892 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10225] Fix doctest runable examples in python manual
Changes by Alexander Belopolsky belopol...@users.sourceforge.net: Added file: http://bugs.python.org/file20376/issue10225-py3k.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10225] Fix doctest runable examples in python manual
Changes by Alexander Belopolsky belopol...@users.sourceforge.net: Removed file: http://bugs.python.org/file20375/issue10225-py3k.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1488934] file.write + closed pipe = no error
Antoine Pitrou pit...@free.fr added the comment: Agreed with Charles-François, this is normal behaviour since the bytes written on stdout are buffered (up to a certain size). If calling flush() doesn't solve the issue, please reopen the issue. -- resolution: - invalid status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1488934 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9941] Unify trace and profile interfaces
Changes by Alexander Belopolsky belopol...@users.sourceforge.net: -- versions: +Python 3.3 -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9941 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10896] trace module compares directories as strings (--ignore-dir)
Vladimir Rutsky rutsky.vladi...@gmail.com added the comment: Workaround for people on Windows who don't wan't to modify trace.py: to get clean trace of only your project calls add to ignore list python path with mix of character cases. For me worked out this string: python -m trace --ignore-dir=c:\python26\lib;C:\python26\lib;C:\Python26\Lib -t main.py -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10896 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10225] Fix doctest runable examples in python manual
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: Committed the simple fixes in r87957. Updated the patch to include only the remaining changes. -- Added file: http://bugs.python.org/file20377/issue10225-py3k.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10225] Fix doctest runable examples in python manual
Changes by Alexander Belopolsky belopol...@users.sourceforge.net: Removed file: http://bugs.python.org/file20376/issue10225-py3k.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10896] trace module compares directories as strings (--ignore-dir)
SilentGhost ghost@gmail.com added the comment: It's due to the os.path.normpath not normalizing case. Here is the patch. Also affects 3.x -- keywords: +patch nosy: +SilentGhost versions: +Python 3.1, Python 3.2 Added file: http://bugs.python.org/file20378/trace.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10896 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue766910] fix one or two bugs in trace.py
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: On Sat, Dec 4, 2010 at 3:34 AM, Eli Bendersky rep...@bugs.python.org wrote: .. However, while experimenting, I think I ran into much larger problems. Either that or I've forgotten how to use the module :-) I am afraid it is the latter. :-) The file specified in --file option should be a pickle, not a coverage file from the previous run. $ ./python.exe -m trace -s -f counts.pickle -c trace_target.py K is 380 Skipping counts file 'counts.pickle': [Errno 2] No such file or directory: 'counts.pickle' lines cov% module (path) 1 100% trace (/Users/sasha/Work/python-svn/py3k-commit/Lib/trace.py) 9 100% trace_target (trace_target.py) 6 100% traced_module (traced_module.py) $ ./python.exe -m pickletools counts.pickle 0: (MARK 1: }EMPTY_DICT 2: qBINPUT 0 4: (MARK 5: (MARK 6: XBINUNICODE 'trace_target.py' ... However, there is a problem here, I think: $ ./python.exe -m trace -s -f counts.pickle -c trace_target.py K is 380 lines cov% module (path) 1 100% trace (/Users/sasha/Work/python-svn/py3k-commit/Lib/trace.py) 9 100% trace_target (trace_target.py) 6 100% traced_module (traced_module.py) $ ./python.exe -m trace -s -f counts.pickle -c trace_target.py K is 380 lines cov% module (path) 1 100% trace (/Users/sasha/Work/python-svn/py3k-commit/Lib/trace.py) 9 100% trace_target (trace_target.py) 6 100% traced_module (traced_module.py) The counts should grow in repeated runs. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue766910 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10896] trace module compares directories as strings (--ignore-dir)
Changes by SilentGhost ghost@gmail.com: -- nosy: +belopolsky ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10896 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10894] Making stdlib APIs private
Changes by Benjamin Peterson benja...@python.org: -- dependencies: +Private stdlib API: getopt, getpass, glob, gzip, genericpath, gettext ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10894 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10896] trace module compares directories as strings (--ignore-dir)
Changes by Antoine Pitrou pit...@free.fr: -- stage: - patch review type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10896 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10895] Private stdlib API: getopt, getpass, glob, gzip, genericpath, gettext
SilentGhost ghost@gmail.com added the comment: Attached patch is fro gettext None of the public members of the module has any docstrings. I'm not sure that simple copying from Doc/library/gettext.rst would be satisfactory. But if it is, please let me know. -- Added file: http://bugs.python.org/file20379/gettext_api.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10895 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10897] UNIX mmap unnecessarily dup() file descriptor
Éric Araujo mer...@netwok.org added the comment: Thanks for the report and patch. Can you refresh it against the py3k branch? Bugs are fixed there and then backported to 3.1 and 2.7. If possible, please include a test in your patch. -- nosy: +eric.araujo, facundobatista, georg.brandl, josiahcarlson, pitrou stage: - patch review versions: -Python 2.5, Python 2.6, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10897 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10894] Making stdlib APIs private
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10894 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1488934] file.write + closed pipe = no error
Erik Demaine edema...@mit.edu added the comment: msg28537 shows a version with flush, and says that it fails. I haven't tested since 2006, though, so I can retry, in particular to see whether the patch suggested in the original post has been applied now. -- resolution: invalid - status: closed - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1488934 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10895] Private stdlib API: getopt, getpass, glob, gzip, genericpath, gettext
Changes by Éric Araujo mer...@netwok.org: -- nosy: +brett.cannon, eric.araujo, rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10895 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4953] cgi module cannot handle POST with multipart/form-data in 3.0
R. David Murray rdmur...@bitdance.com added the comment: Yes, the immanence of RC1 makes it really doubtful that this can be fixed in 3.2. Whether or not it can be fixed in 3.2.1 will depend on the nature of the fix. If it changes behavior such that currently working uses of FieldStorage (that don't deal with binary files) break, then the fix can't be backported. Likewise if the API changes, the change can't be backported. Doing the deprecation sounds like a good idea. Would you be willing to propose a patch with tests? I'm pretty busy this week and I doubt I can do anything myself about it before the weekend. If this cannot be fixed in a way that is backward compatible (and even if it can), in 3.3 we also have the option of adding features to the email package to better support the use cases in HTTP if that makes sense. Certainly the external file support is something that email needs for itself, so it would be nice to add that in 3.3. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4953 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10897] UNIX mmap unnecessarily dup() file descriptor
Changes by SilentGhost ghost@gmail.com: -- nosy: +SilentGhost ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10897 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1488934] file.write + closed pipe = no error
Antoine Pitrou pit...@free.fr added the comment: msg28537 shows a version with flush, and says that it fails I cannot reproduce. Either with Python 2.5.2 (!), 2.7 or 3.2, on a remote Debian system. Even using kill -9 on the local ssh process does shut down the remote Python process. If I comment out the flush() call, it is clearly reproduceable. I would suggest you did something wrong when testing the flush() version. -- resolution: - invalid stage: unit test needed - status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1488934 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1488934] file.write + closed pipe = no error
Erik Demaine edema...@mit.edu added the comment: I just tested on Python 2.5.2, 2.6.2, and 3.0.1, and I could not reproduce the error (using the code in msg28537). It would seem that file.flush is catching the problem, even though file.write is ignoring the error, but I can't see any changes since 1.5.2 that would have changed this behavior of file.flush. So I'm not sure what happened, but at least it seems to no longer be a bug. Closing. -- status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1488934 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10898] posixmodule.c redefines FSTAT
New submission from Alan Hourihane al...@fairlite.co.uk:
Python 2.7.1 redefines FSTAT, but the problem is my libc already defines FSTAT
in sys/ioctl.h.
I've worked around this by prefixing the FSTAT define with PYTHON. It should
probably be done with STAT too.
--- Modules/posixmodule.c.old 2011-01-12 01:46:45.0 +
+++ Modules/posixmodule.c 2011-01-12 01:47:05.0 +
@@ -344,11 +344,11 @@
#undef STAT
#if defined(MS_WIN64) || defined(MS_WINDOWS)
# define STAT win32_stat
-# define FSTAT win32_fstat
+# define PYTHON_FSTAT win32_fstat
# define STRUCT_STAT struct win32_stat
#else
# define STAT stat
-# define FSTAT fstat
+# define PYTHON_FSTAT fstat
# define STRUCT_STAT struct stat
#endif
@@ -6641,7 +6641,7 @@
if (!_PyVerify_fd(fd))
return posix_error();
Py_BEGIN_ALLOW_THREADS
-res = FSTAT(fd, st);
+res = PYTHON_FSTAT(fd, st);
Py_END_ALLOW_THREADS
if (res != 0) {
#ifdef MS_WINDOWS
--
messages: 126120
nosy: alanh
priority: normal
severity: normal
status: open
title: posixmodule.c redefines FSTAT
type: compile error
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10898
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9880] GCC 4.6 bug with -ftree-vectorize
STINNER Victor victor.stin...@haypocalc.com added the comment: I reported the bug to GCC: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47271 -- title: Python 2.7 Won't Build: SystemError: unknown opcode - GCC 4.6 bug with -ftree-vectorize ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9880 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10894] Making stdlib APIs private
Brett Cannon br...@python.org added the comment: I will be writing a proper task item for this (there's a reason it's a todo item =), but I will read this before writing it so feel free to leave any thoughts or ideas for the future task. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10894 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10895] Private stdlib API: getopt, getpass, glob, gzip, genericpath, gettext
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: -0 It is questionable whether this should be done at all. Either it is irrelevant or it will break someone's code. -- priority: normal - low ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10895 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10894] Making stdlib APIs private
Changes by SilentGhost ghost@gmail.com: -- nosy: +rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10894 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4953] cgi module cannot handle POST with multipart/form-data in 3.0
Glenn Linderman v+pyt...@g.nevcal.com added the comment: I'd be willing to propose such a patch and tests, but I haven't a clue how, other than starting by reading the contributor document... I was putting off learning the process until hg conversion, not wanting to learn an old process for a few months :( And I've never written an official Python test, or learned how to use the test modules, etc. So that's a pretty steep curve for the 2 days remaining. Due to the way that browsers actually work, vs. how the standards are written, it seems necessary to add the optional stream_encoding parameter. The limit parameter Pierre is proposing is also a good check against improperly formed inputs. So there are new, optional parameters to the FieldStorage constructor. Without these fixes, though, cgi.py continues to be totally useless for file uploads, so not releasing this in 3.2 makes 3.2 continue to be useless as a basis for web applications. I have no idea if there is a timeframe for 3.3, nor what it is. I'm not sure if, or how many, web frameworks use cgi.py vs. replacing the functionality. Seems at least some replace it, so they may not suffer in porting to 3.x (except internally, grappling with the same issues). Happily, Pierre's latest patch needs only one more fix, per my (non-Python-standard) testing. Between his testing in one environment using default code pages, and mine using UTF-8, the bases seem to be pretty well covered for testing... certainly more than the previous default tests. I think you contributed some tests, I haven't tried them, but it seems Pierre has, as he has a patch for that also (which I haven't tried). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4953 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10822] test_getgroups failure under Solaris
Antoine Pitrou pit...@free.fr added the comment: Thanks for the patch! Committed in r87958 (3.2), r87959 (3.1) and r87961 (2.7). -- resolution: - fixed stage: needs patch - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10822 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10897] UNIX mmap unnecessarily dup() file descriptor
SilentGhost ghost@gmail.com added the comment: version of the lorenz's patch agains py3k branch. -- Added file: http://bugs.python.org/file20380/mmap.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10897 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10897] UNIX mmap unnecessarily dup() file descriptor
Antoine Pitrou pit...@free.fr added the comment: The problem is that it's a change in semantics. So it definitely can't be backported to the bugfix branches, nor committed into 3.2 which is in feature freeze now. The question is which behaviour is the most expected by users of the module. I'd say that dup()ing definitely isn't intuitive, and it isn't documented; on the other hand, at least one of the examples seems to assume the original file descriptor is untouched when close()ing the mmap object: with open(hello.txt, r+b) as f: # memory-map the file, size 0 means whole file map = mmap.mmap(f.fileno(), 0) # read content via standard file methods print(map.readline()) # prints bHello Python!\n # read content via slice notation print(map[:5]) # prints bHello # update content using slice notation; # note that new content must have same size map[6:] = b world!\n # ... and read again using standard file methods map.seek(0) print(map.readline()) # prints bHello world!\n # close the map map.close() -- versions: +Python 3.3 -Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10897 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10893] The docs mark staticmethod as a function
Changes by Raymond Hettinger rhettin...@users.sourceforge.net: -- resolution: - invalid status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10893 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10894] Making stdlib APIs private
Antoine Pitrou pit...@free.fr added the comment: My take on this: - adding underscores to locally-defined private functions is good. +1 - -0.5 on from warnings import warn as _warn; it's useless complication, users should be able to realize warn() is a public API of the warnings module, not whichever else module using it -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10894 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10894] Making stdlib APIs private
Antoine Pitrou pit...@free.fr added the comment: Oh, by the way, it can be good to check that the APIs are not used too widely. Example for such a query: http://www.google.com/codesearch?q=lang%3Apython%20do_longshl=fr (in this case, it's clear that only copies of the stdlib reference that function) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10894 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10855] wave.Wave_read.close() doesn't release file
Georg Brandl ge...@python.org added the comment: I don't really see the bug here. Either you openened the file object, then you have to close it. Or wave.py opened it, then it will close it, no matter if it still has a reference or not. Of course we could set _data_chunk to None, but I'm unsure what behavior change you would expect from that. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10855 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10855] wave.Wave_read.close() doesn't release file
Antoine Pitrou pit...@free.fr added the comment: Agreed with Georg. No OS resource is leaking if the file is explicitly closed (since it releases the underlying file descriptor). That the Python file object is still attached somewhere is of secondary importance. -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10855 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10874] test_urllib2 shouldn't use is operator for comparing strings
SilentGhost ghost@gmail.com added the comment: Committed for 2.7 in r87964, for 3.1 in r87965. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10855] wave.Wave_read.close() doesn't release file
Peter Creath pjcreath+pyt...@gmail.com added the comment: A point of clarification on the original report: Georg is completely right when he points out that this is only an issue when passing in a file object. If passed a filename, wave.py both opens and closes the file explicitly, and the dangling reference isn't important, as Antoine observes. However, a retained reference in the file-object case is still a leak. Georg writes: Of course we could set _data_chunk to None, but I'm unsure what behavior change you would expect from that. It allows garbage collection to close the file object if there are no more references to it. It seems reasonable for a client of wave.py to assume that close() will release all references to the object, and indeed the code seems to support that assumption -- it sets _file to None. If releasing references were truly of no importance, then I would argue that the line setting _file to None should be removed. It serves no purpose after wave.py has explicitly closed the file (if it opened it) other than to release a reference to the file object. Therefore, I suggest that _data_chunk should also be set to None in order to release the reference completely, thereby allowing the file object to be garbage collected. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10855 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10897] UNIX mmap unnecessarily dup() file descriptor
Lorenz Huedepohl lor...@mpa-garching.mpg.de added the comment: Thanks SilentGhost, you were much faster than me :) I agree with Antoine, that the dup() is unexpected: It cost me some time to figure out where these additonal file descriptors originated from. One of the powers of mmap() is, that you do not need one, so it would really be great if this feature could be saved into the python abstraction. As for the example: I think this could be cured by removing the close(m_obj-fd); statement, again shifing the responsibility for that to the creator of the intial file handle - see my attached patch. (This time against the py3k patch) BTW: It is a great experience for a python user to see just how fast you guys react to an issue here! Thanks! -- Added file: http://bugs.python.org/file20381/no_dup_no_close.py3k.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10897 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8771] Socket freezing under load issue on Mac.
Charles-Francois Natali neolo...@free.fr added the comment:
As explained by Jean-Paul, it's due to the fact that the closed TCP sockets
spend some time in TIME-WAIT state before being deallocated.
On Linux, this issue can be more or less worked-around using sysctl
(net.ipv4.tcp_tw_{reuse,recycle}). There might be something similar on OS-X.
It's definitely an OS-level tuning issue.
Suggesting to close.
--
nosy: +neologix
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8771
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8771] Socket freezing under load issue on Mac.
Alice Bevan-McGregor al...@gothcandy.com added the comment: Agreed; I'm now certain it's a local tuning issue. My first attempt to alter the file descriptor limits for local testing resulted in catastrophic system failure, though, so I have no clue as to the correct method to alter the TIME_WAIT time. I will continue to investigate, thank you for the lead. -- resolution: - invalid status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8771 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10855] wave.Wave_read.close() doesn't release file
Antoine Pitrou pit...@free.fr added the comment: It allows garbage collection to close the file object if there are no more references to it. This is a very bad policy to begin with. Garbage collection can be delayed for a number of reasons: - someone might be running your program on a Python implementation which doesn't use reference counting (such as Jython or PyPy) - an exception, together with its traceback object, might capture the value of some local variables and keep them alive (that is, reachable from the GC's point of view) - a reference cycle might delay proper resource cleanup until the cyclic garbage collector kicks in So the good thing to do is to close your file explicitly. Luckily, Python 2.6 and upwards makes it easier by using the with statement. IMO this issue should be closed. -- resolution: - rejected stage: unit test needed - status: open - pending versions: -Python 2.5, Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10855 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2650] re.escape should not escape underscore
yeswanth swamiyeswa...@yahoo.com added the comment: As James said I have written the patch using only regular expressions . This is going to be my first patch . I need help writing the test for it -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2650 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9124] Mailbox module should use binary I/O, not text I/O
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: RDM, you were suggested for this by Thomas Wouters (who wrote much of the existing code). Are you up for it? -- assignee: - r.david.murray nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9124 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4953] cgi module cannot handle POST with multipart/form-data in 3.0
Pierre Quentel pierre.quen...@gmail.com added the comment: Many thoughts and tests after... Glenn, the both of us were wrong : the encoding to use in FieldStorage is neither latin-1, nor sys.stdin.encoding : I tested form fields with characters whose utf-8 encoding has bytes that map to undefined in cp1252, the calls to the decode() method with sys.stdin.encoding failed The encoding used by the browser is defined in the Content-Type meta tag, or the content-type header ; if not, the default seems to vary for different browsers. So it's definitely better to define it The argument stream_encoding used in FieldStorage *must* be this encoding ; in this version, it is set to utf-8 by default But this raises another problem, when the CGI script has to print the data received. The built-in print() function encodes the string with sys.stdout.encoding, and this will fail if the string can't be encoded with it. It is the case on my PC, where sys.stdout.encoding is cp1252 : it can't handle Arabic or Chinese characters The solution I have tried is to pass another argument, charset, to the FieldStorage contructor, defaulting to utf-8. It must be the same as the charset defined in the CGI script in the Content-Type header FieldStorage uses this argument to override the built-in print() function : - flush the text layer of sys.stdin, in case calls to print() have been made before calling FieldStorage - get the binary layer of stdout : out = sys.stdout.detach() - define a function _print this way: def _print(*strings): for item in strings: out.write(str(item).encode(charset)) out.write(b'\r\n') - override print() : import builtins builtins.print = _print The function print() in the CGI script now sends the strings encoded with charset to the binary layer of sys.stdout. All the tests I made with Arabic or Chinese input fileds, or file names, succed when using this patch ; so do test_cgi and cgi_test (slightly modified) -- Added file: http://bugs.python.org/file20382/cgi_diff_20110112.txt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4953 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2650] re.escape should not escape underscore
Antoine Pitrou pit...@free.fr added the comment: As James said I have written the patch using only regular expressions . This is going to be my first patch . I need help writing the test for it You will find the current tests in Lib/test/test_re.py. To execute them, run: $ ./python -m test.regrtest -v test_re In this case, there are probably already some tests for re.escape. So you have to check that they are sufficient, and that your patch doesn't make them fail. -- stage: - needs patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2650 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1172711] long long support for array module
Matt Chaput m...@sidefx.com added the comment: This is an important feature to me. Now I get to redo a bunch of code to have two completely different code paths to do the same thing because nobody could be bothered to keep array up-to-date. -- nosy: +mattchaput ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1172711 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10899] No function type annotations in the standard library
New submission from Raymond Hettinger rhettin...@users.sourceforge.net: The discussion for PEP 3107 said the use and interpretation of function type annotations was being left open for third-party developers to use as they see fit (some may use strings, other ABCs, others concrete types, or tuples of types or some other structure). Accordingly, we're not used them in the standard library because that would trump third-party uses. The exception is in the file Lib/_pyio.py which has a number of function annotations. I think those annotations should be replaced with comments. As it stands, they're untested, undocumented, and at odds with our idea to let the rest of the world decide how and when to use function type annotations. Guido, I think you pronounced on this a long time ago. Unfortunately, the PEP stops just short of saying don't use this in the standard library and the email threads are too voluminous to re-read. So, I wanted to ask, what do you think now? My vote is keep the stdlib out of the function type annotation business. -- Excerpts from the PEP: The only way that annotations take on meaning is when they are interpreted by third-party libraries. These annotation consumers can do anything they want with a function's annotations. For example, one library might use string-based annotations to provide improved help messages, like so ... this PEP makes no attempt to introduce any kind of standard semantics, even for the built-in types. This work will be left to third-party libraries. Though discussed early on ([5], [6]), including special objects in the stdlib for annotating generator functions and higher-order functions was ultimately rejected as being more appropriate for third-party libraries; including them in the standard library raised too many thorny issues. Despite considerable discussion about a standard type parameterisation syntax, it was decided that this should also be left to third-party libraries. Despite yet more discussion, it was decided not to standardize a mechanism for annotation interoperability. Standardizing interoperability conventions at this point would be premature. We would rather let these conventions develop organically, based on real-world usage and necessity, than try to force all users into some contrived scheme. -- assignee: gvanrossum messages: 126143 nosy: collinwinter, gvanrossum, rhettinger priority: normal severity: normal status: open title: No function type annotations in the standard library versions: Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10899 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9124] Mailbox module should use binary I/O, not text I/O
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: With the module being so slow as to be unusable, this can be considered a bugfix, so it is okay if the fix goes into 3.2.1. -- versions: -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9124 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8771] Socket freezing under load issue on Mac.
Changes by Terry J. Reedy tjre...@udel.edu: -- nosy: -terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8771 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4953] cgi module cannot handle POST with multipart/form-data in 3.0
Peter Kleiweg pklei...@xs4all.nl added the comment: Pierre Quentel wrote: - get the binary layer of stdout : out = sys.stdout.detach() You can't do that! That makes sys.stdout unavaible to the program that is importing the cgi module. Cgi should access and process sys.stdin only, as binary by means of sys.stdin.detach() The cgi module is used to handle form data and uploaded files. But the resulting page is usually written by the main program or another module, using sys.stdout -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4953 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9880] GCC 4.6 bug with -ftree-vectorize
Georg Brandl ge...@python.org added the comment: Do we have to keep this open? -- nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9880 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9880] GCC 4.6 bug with -ftree-vectorize
STINNER Victor victor.stin...@haypocalc.com added the comment: Do we have to keep this open? Nope, let's close it. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9880 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10899] No function type annotations in the standard library
Guido van Rossum gu...@python.org added the comment: On the one hand, I think that any framework that sets a convention for the meaning of annotations needs to cope with the possibility of other code using a different convention. So in that sense this could be deemed a test case for the robustness of such a framework. :-) On the other hand, having this precedent might give passers-by and perhaps future stdlib developers the idea that a convention has been adopted by the stdlib -- and its presence might impede the future selection of a better convention for the stdlib (or perhaps for all of Python). So, given that they aren't used, and that they don't even seem to be set consistently, I think it's (marginally) better if they are removed and replaced by comments. FWIW, I've long wished that the stdlib (and perhaps even PEP 8) would adopt a *comment-based* convention for indicating the types of arguments. The Google Python style guide has a useful standard convention for this purpose: http://google-styleguide.googlecode.com/svn/trunk/pyguide.html?showone=Comments#Comments -- assignee: gvanrossum - rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10899 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10899] No function type annotations in the standard library
Antoine Pitrou pit...@free.fr added the comment: On the other hand, having this precedent might give passers-by and perhaps future stdlib developers the idea that a convention has been adopted by the stdlib Could we simply state in PEP 8 that annotations have no official meaning and that anyone (including stdlib developers) can use it for whatever purpose they see fit? FWIW, I've long wished that the stdlib (and perhaps even PEP 8) would adopt a *comment-based* convention for indicating the types of arguments. You mean docstring-based? -- assignee: rhettinger - components: +IO, Library (Lib) nosy: +pitrou versions: +Python 3.3 -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10899 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10899] No function type annotations in the standard library
Guido van Rossum gu...@python.org added the comment: On Wed, Jan 12, 2011 at 2:49 PM, Antoine Pitrou rep...@bugs.python.org wrote: Could we simply state in PEP 8 that annotations have no official meaning and that anyone (including stdlib developers) can use it for whatever purpose they see fit? No, that is less strong than what I said. I agree with Raymond that they should be kept out of the stdlib until we've come up with a convention. FWIW, I've long wished that the stdlib (and perhaps even PEP 8) would adopt a *comment-based* convention for indicating the types of arguments. You mean docstring-based? Sorry, yes. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10899 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10899] No function type annotations in the standard library
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: Thanks for the quick reply. Checked-in. See r87977 and r87978. -- resolution: - fixed status: open - closed versions: +Python 3.1 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10899 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4953] cgi module cannot handle POST with multipart/form-data in 3.0
Glenn Linderman v+pyt...@g.nevcal.com added the comment: Pierre said: The encoding used by the browser is defined in the Content-Type meta tag, or the content-type header ; if not, the default seems to vary for different browsers. So it's definitely better to define it The argument stream_encoding used in FieldStorage *must* be this encoding I say: I agree it is better to define it. I think you just said the same thing that the page I linked to said, I might not have conveyed that correctly in my paraphrasing. I assume you are talking about the charset of the Content-Type of the form page itself, as served to the browser, as the browser, sadly, doesn't send that charset back with the form data. Pierre says: But this raises another problem, when the CGI script has to print the data received. The built-in print() function encodes the string with sys.stdout.encoding, and this will fail if the string can't be encoded with it. It is the case on my PC, where sys.stdout.encoding is cp1252 : it can't handle Arabic or Chinese characters I say: I don't think there is any need to override print, especially not builtins.print. It is still true that the HTTP data stream is and should be treated as a binary stream. So the script author is responsible for creating such a binary stream. The FieldStorage class does not use the print method, so it seems inappropriate to add a parameter to its constructor to create a print method that it doesn't use. For the convenience of CGI script authors, it would be nice if CGI provided access to the output stream in a useful way... and I agree that because the generation of an output page comes complete with its own encoding, that the output stream encoding parameter should be separate from the stream_encoding parameter required for FieldStorage. A separate, new function or class for doing that seems appropriate, possibly included in cgi.py, but not in FieldStorage. Message 125100 in this issue describes a class IOMix that I wrote and use for such; codifying it by including it in cgi.py would be fine by me... I've been using it quite successfully for some months now. The last line of Message 125100 may be true, perhaps a few more methods should be added. However, print is not one of them. I think you'll be pleasantly surprised to discover (as I was, after writing that line) that the builtins.print converts its parameters to str, and writes to stdout, assuming that stdout will do the appropriate encoding. The class IOMix will, in fact, do that appropriate encoding (given an appropriate parameter to its initialization. Perhaps for CGI, a convenience function could be added to IOMix to include the last two code lines after IOMix in the prior message: @staticmethod def setup( encoding=UTF-8): sys.stdout = IOMix( sys.stdout, encoding ) sys.stderr = IOMix( sys.stderr, encoding ) Note that IOMix allows the users choice of output stream encoding, applies it to both stdout and stderr, which both need it, and also allows the user to generate binary directly (if sending back a file, for example), as both bytes and str are accepted. print can be used with a file= parameter in 3.x which your implementation doesn't permit, and which could be used to write to other files by a CGI script, so I really, really don't think we want to override builtins.print without the file= parameter, and specifically tying it to stdout. My message 126075 still needs to be included in your next patch. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4953 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9124] Mailbox module should use binary I/O, not text I/O
R. David Murray rdmur...@bitdance.com added the comment: I've been intending to take a look at this issue at some point, but am not sure when I'd get to it. I took a quick look. It does seems to me that it is true that for data-validity purposes the message files need to be opened in binary and fed to the email package in binary. But this is so that the message will get decoded using the correct character sets, not to avoid the decoding. In Python3 it makes no sense to manipulate the subjects as binary strings, so the example of looping through the messages and printing the subjects is still going to require decoding. There may still be ways to make it more efficient for common use cases, but that will require more detailed analysis. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9124 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2650] re.escape should not escape underscore
Changes by SilentGhost ghost@gmail.com: -- nosy: +SilentGhost ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2650 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue766910] fix one or two bugs in trace.py
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: On Wed, Jan 12, 2011 at 12:17 PM, Alexander Belopolsky rep...@bugs.python.org wrote: .. The counts should grow in repeated runs. I did not pay attention: the numbers in summary are numbers of lines, not execution counts. The execution counts in .cover file grow as expected. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue766910 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue766910] fix one or two bugs in trace.py
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: On Sat, Dec 4, 2010 at 3:34 AM, Eli Bendersky rep...@bugs.python.org wrote: .. I reviewed the patch and ported the changes to the newest sources Eli, I don't think you ever posted an updated patch. Do you still have it? This may be a good starting issue for you as a committer. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue766910 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10899] No function type annotations in the standard library
Brett Cannon br...@python.org added the comment: You missed importlib/abc.py which uses the annotations to document the types of method arguments (and their return values), e.g., what Guido said he might use the annotations for. -- nosy: +brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10899 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
