[issue10516] Add list.clear() and list.copy()
Changes by Eli Bendersky eli...@gmail.com: -- nosy: +eli.bendersky ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10516 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build
Ezio Melotti ezio.melo...@gmail.com added the comment: I agree that s.center(char, n).encode('utf-8') should be the same on both the builds -- even if their len() will be different -- for the following reasons: 1) the string will eventually be encoded, and if they the result is the same on both builds, it will look the same too; 2) trying to keep the same len() will generate different results and it won't work in case of odd width like 'foo'.center(surrogate_pair, 5) because you can't put half surrogate. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10521 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10541] regrtest.py -T broken
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: Apparently something in the test changes the cwd. Both of the following invocations work: $ ./python.exe `pwd`/Lib/test/regrtest.py -T -N test_urllib $ ./python.exe -m test.regrtest -T -N test_urllib I would suggest changing the coverage target in the Makefile. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10541 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9264] trace.py documentation is incomplete
Eli Bendersky eli...@gmail.com added the comment: Éric, good idea - I'll do it. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9264 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9264] trace.py documentation is incomplete
Eli Bendersky eli...@gmail.com added the comment: There's something weird going on with cmdoption... I've applied for subscription to the docs mailing list, but while I'm awaiting moderator approval, here's the brain-dump. Suppose this option description: .. program:: trace .. cmdoption:: -c, --count Blah blah blah And now this reference: This is a test long :option:`--count` and then short :option:`-c`, test. Only the -c gets linked to ..cmdoption, not --count. If I list --count before -c in ..cmdoption, then it's the other way around. What makes it kinda work (link both the long and short names) is: .. cmdoption:: -c --count Blah blah blah But this isn't standard (although it doesn't look too bad). Actually, the original listing (the short name first, then the long one) is customary in the library docs. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9264 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10242] unittest's assertItemsEqual() method makes too many assumptions about its input
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: Applied in r86828. The output could still be made nicer, perhaps something along the lines of: expected 6, got 4: 'wand of fireballs' expected 2, got 7: 'ring of invisibility' . . . -- priority: high - normal resolution: - fixed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10242 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10544] yield expression inside generator expression does nothing
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: Hmm, what an interesting and unexpected side-effect of the efforts to hide the loop induction variable. -- nosy: +rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10544 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10516] Add list.clear() and list.copy()
Eli Bendersky eli...@gmail.com added the comment: Objects/listobject.c has a static function named list_clear used internally. Is it possible to just expose this function as a clear() method? One problem is that it has this strange comment in the end: /* Never fails; the return value can be ignored. Note that there is no guarantee that the list is actually empty at this point, because XDECREF may have populated it again! */ However, looking at the code I'm not sure the list can be cleared any more than the function does, and it actually deallocates the ob_item field of the list. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10516 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10242] unittest's assertItemsEqual() method makes too many assumptions about its input
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: Attaching possible code for nicer output. -- assignee: rhettinger - michael.foord resolution: fixed - Added file: http://bugs.python.org/file19833/nice_output.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10242 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10516] Add list.clear() and list.copy()
Xuanji Li xua...@gmail.com added the comment: Hi, I'm also looking at listobject.c also... if we want list.clear() to behave exactly like del list[], we may be able to just call list_ass_slice on the list. Similarly for list.copy which should behave like a=l[:] -- nosy: +xuanji ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10516 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10516] Add list.clear() and list.copy()
Eli Bendersky eli...@gmail.com added the comment: Hi, I'm also looking at listobject.c also... if we want list.clear() to behave exactly like del list[], we may be able to just call list_ass_slice on the list. Similarly for list.copy which should behave like a=l[:] Note that when executed to do 'del lst[:]' (i.e. with argument v set to 0 and ilow/ihigh to the maximal range of the list), list_ass_slice will just call list_clear anyway, which is a cue that this indeed is the right way to do it, despite the strange comment I mentioned in my message above. -- Added file: http://bugs.python.org/file19834/unnamed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10516 ___div dir=ltrbrdiv class=gmail_quoteblockquote class=gmail_quote style=margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex; br Hi, I#39;m also looking at listobject.c also... if we want list.clear() to behave exactly like del list[], we may be able to just call list_ass_slice on the list. Similarly for list.copy which should behave like a=l[:]br /blockquote/divbrNote that when executed to do #39;del lst[:]#39; (i.e. with argument v set to 0 and ilow/ihigh to the maximal range of the list), list_ass_slice will just call list_clear anyway, which is a cue that this indeed is the right way to do it, despite the strange comment I mentioned in my message above.br br/div ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10516] Add list.clear() and list.copy()
Georg Brandl ge...@python.org added the comment: Yes, list_clear should be called, but no, it cannot be used directly because a method needs a PyObject* return value. So a wrapper method is needed that looks like listappend() does for list.append(). list_copy() will just look like list_slice() with the index fiddling removed. -- nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10516 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10542] Py_UNICODE_NEXT and other macros for surrogates
Marc-Andre Lemburg m...@egenix.com added the comment: Raymond Hettinger wrote: Raymond Hettinger rhettin...@users.sourceforge.net added the comment: Mark, can you opine on this? Yes, I'll have a look later today. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10542 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10383] test_os leaks under Windows
Stefan Krah stefan-use...@bytereef.org added the comment: Fixed original leaks in r86804, r86806 and r86804. Fixed additional leaks in r86829. -- components: +Extension Modules -Library (Lib), Windows resolution: - fixed stage: - committed/rejected status: open - closed versions: +Python 2.7, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10383 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10516] Add list.clear() and list.copy()
Xuanji Li xua...@gmail.com added the comment: That's good if it's so... can you explain why list_clear doesn't guarantee that the list is empty? Why would XDECREF populate the list? I don't quite understand it. eli: are you writing a patch for this? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10516 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9264] trace.py documentation is incomplete
Éric Araujo mer...@netwok.org added the comment: I noticed too that the second form given in a cmdoption directive cannot be linked to from an option construct. The workaround looks like this: :option:`--long -l`. This uses a generic Sphinx (or reST) property: When using :role:`text thing`, “thing” will be given as argument to the role but “text” will be displayed. It’s very useful for references for example, if you don’t want title case in the middle of your sentence of if you need to rephrase the title: “Have a look at the :ref:`detailed explanation config-explanation`”. Even if it can be worked around, can you report this Sphinx bug? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9264 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10516] Add list.clear() and list.copy()
Eli Bendersky eli...@gmail.com added the comment: Georg, Thanks. Of course it should be wrapped like the others :-) Xuanji, Yes, I will try to get in something preliminary today. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10516 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9264] trace.py documentation is incomplete
Eli Bendersky eli...@gmail.com added the comment: Éric, I sent an inquiry about this problem to the d...@python.org list. In the meantime, I will implement it with the workaround you suggest (I checked it works in this case too). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9264 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10516] Add list.clear() and list.copy()
Eli Bendersky eli...@gmail.com added the comment: Attaching a patch for list.clear(): 1. Implements a new function in Objects/listobject.c named listclear() (to be consistent with the other method functions) 2. listclear() is registered in list_methods and just calls list_clear(), returning None 3. A documentation string is modeled after dict.clear(), but shaped a bit differently to follow the conventions of other list method docs. If this look fine to the more experienced devs, things left to do are: 1. Add tests 2. Implement the .copy() method in a similar manner + tests for it Some random observations: 1. The naming of functions/methods could be made more consistent. See, for example, list_reversed vs. listreverse. 2. The documentation style of list and dict methods is different for no apparent reason: help({}.pop) gives: pop(...) D.pop(k[,d]) - v, remove specified key and return the corresponding value. If key is not found, d is returned if given, otherwise KeyError is raised While help([].pop) gives: pop(...) L.pop([index]) - item -- remove and return item at index (default last). Raises IndexError if list is empty or index is out of range. Note the '--' which separates the signature from description in the list version. -- keywords: +patch Added file: http://bugs.python.org/file19835/issue10516.1.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10516 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10516] Add list.clear() and list.copy()
Changes by Eli Bendersky eli...@gmail.com: Removed file: http://bugs.python.org/file19834/unnamed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10516 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10547] FreeBSD: wrong value for LDSHARED in sysconfig
New submission from Stefan Krah stefan-use...@bytereef.org: On FreeBSD, the config variable LDSHARED contains the literal '${LDFLAGS}', causing this failure in test_distutils: 'test_get_outputs (distutils.tests.test_build_ext.BuildExtTestCase) ... gcc: ': No such file or directory ERROR The patch fixes the issue and all tests pass. Benjamin, are you ok with the change for 2.7? I'm not sure why autoreconf generated a bit of extra noise; I used version 2.65. Also, OpenBSD and NetBSD should be affected as well. -- components: Build files: freebsd_ldshared.patch keywords: needs review, patch messages: 122525 nosy: benjamin.peterson, skrah priority: normal severity: normal stage: patch review status: open title: FreeBSD: wrong value for LDSHARED in sysconfig type: behavior versions: Python 2.7 Added file: http://bugs.python.org/file19836/freebsd_ldshared.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10547 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10547] FreeBSD: wrong value for LDSHARED in sysconfig
Changes by Stefan Krah stefan-use...@bytereef.org: -- keywords: +buildbot -needs review, patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10547 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9264] trace.py documentation is incomplete
Eli Bendersky eli...@gmail.com added the comment: Attaching an updated patch for Doc/library/trace.rst in 3.2 Changed the formatting of command-line options per Éric's suggestion of using program/cmdoption/option combos (great idea Éric - it looks much better). -- Added file: http://bugs.python.org/file19837/issue9264.py32.2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9264 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9509] argparse FileType raises ugly exception for missing file
Steven Bethard steven.beth...@gmail.com added the comment: Tried to comment in Rietveld but it didn't work for some reason. Anyway, I think the argparse.py patch isn't good - changing the type error message to 'invalid %s value: %r details: %s' will change the behavior of a bunch of programs, and it's not clearly for the better. Instead, you should raise an ArgumentTypeError instead of a ValueError, and give it whatever message you want there. That is, let's keep this patch local to the FileType, and not touch the rest of argparse. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9509 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9509] argparse FileType raises ugly exception for missing file
SilentGhost michael.mischurow+...@gmail.com added the comment: Steven, I'm not sure why you're insisting on ArgumentTypeError, when it should be ArgumentError. The file name is not coerced into a different file type, but rather the error occurs when trying to use parameter passed. In any way, my patch is still available. Do you not like something about it? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9509 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9264] trace.py documentation is incomplete
Éric Araujo mer...@netwok.org added the comment: Thanks for your work on this! ``dir/package/module.cover`` → :file:`{dir}/{package}/{module}.cover` '' looks wrong. ``os.pathsep``: You can use :data:`os.pathsep` to get a link, I think. +.. method:: CoverageResults.update(other) FTR, there is a new way for doing such things: You can nest method directives in a class directive block. See gettext.rst for an example. Your patch needn’t change that now, not all docs have been updated, so it’s best to do as you did and follow the style of the rest of the file. I propose to change it after your patch is committed. +.. Stray dots at the end of the file. The doc uses one or two spaces inconsistently. I don’t know if it’s worth changing. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9264 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10548] Error in setUp not reported as expectedFailure (unittest)
New submission from Michael Foord mich...@voidspace.org.uk: Reported by Konrad Delong. class MyTest(unittest.TestCase): def setUp(self): raise Exception @unittest.expectedFailure def testSomething(self): assert False, test method failed This code will report error, not expected failure. -- assignee: michael.foord components: Library (Lib) messages: 122530 nosy: michael.foord priority: normal severity: normal status: open title: Error in setUp not reported as expectedFailure (unittest) type: behavior versions: Python 2.7, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10548 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9264] trace.py documentation is incomplete
Eli Bendersky eli...@gmail.com added the comment: Attaching an updated patch following Éric's suggestions: * ``dir/package/module.cover`` -- FIXED * '' looks wrong -- FIXED to just * ``os.pathsep`` -- FIXED * method:: CoverageResults.update(other) -- OK, let's leave it for a separate issue. * Stray dots at the end of the file -- FIXED * The doc uses one or two spaces inconsistently. -- not 100% what you mean here, but I found inconsistent separation between paragraphs (sometimes 1 blank line, sometimes 2), and fixed it. If you meant something else, I can fix that too :) -- Added file: http://bugs.python.org/file19838/issue9264.py32.3.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9264 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10516] Add list.clear() and list.copy()
Changes by Eli Bendersky eli...@gmail.com: -- Removed message: http://bugs.python.org/msg122522 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10516 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9264] trace.py documentation is incomplete
Éric Araujo mer...@netwok.org added the comment: Duh, I forgot some words: The file uses one or two dots *after full stops* inconsistently. I don’t think you have to change that now, we can make it consistent later (or not, as it does not affect the output), as we do with line wrapping. Just keep it in mind for future patches :) Terry: I got no warnings when building the HTML and the output looks good. +1 on commit. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9264 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10531] write tilted text in turtle
Joe Metcalfe j.g.metca...@gmail.com added the comment: Turtle is built on top of Tk, which is currently at version 8.5 - this has no ability to rotate text. When Tk version 8.6 arrives it should be able to write rotated text (see http://mail.python.org/pipermail/tkinter-discuss/2010-November/002490.html) and turtle.py could be updated to take advantage of it. -- nosy: +Joe.Metcalfe ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10531 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10531] write tilted text in turtle
Changes by Joe Metcalfe j.g.metca...@gmail.com: -- versions: -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10531 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4111] Add Systemtap/DTrace probes
Jesús Cea Avión j...@jcea.es added the comment: Some references to keep around: http://src.opensolaris.org/source/xref/jds/spec-files/trunk/patches/ http://src.opensolaris.org/source/xref/jds/spec-files/trunk/patches/Python26-07-dtrace.diff http://src.opensolaris.org/source/xref/jds/spec-files/trunk/patches/Python-07-dtrace.diff -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4111 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10549] help(cls1) breaks when cls1 has staticmethod(cls2) attribute
New submission from Milko Krachounov pyt...@milko.3mhz.net: If I make a class B, and add staticmethod(A) as an attribute when B is another class, help(B) breaks. The issue appears with Python 2.6.6, trunk, 3.1.3c1, and py3k SVN. Python 2.7 (trunk:86836, Nov 27 2010, 18:23:07) [GCC 4.4.5] on linux2 Type help, copyright, credits or license for more information. class A(object): ... pass ... class B(object): ... attr = staticmethod(A) ... help(B) Traceback (most recent call last): File stdin, line 1, in module File /home/milko/Среда/Python/trunk/Lib/site.py, line 453, in __call__ return pydoc.help(*args, **kwds) File /home/milko/Среда/Python/trunk/Lib/pydoc.py, line 1720, in __call__ self.help(request) File /home/milko/Среда/Python/trunk/Lib/pydoc.py, line 1767, in help else: doc(request, 'Help on %s:') File /home/milko/Среда/Python/trunk/Lib/pydoc.py, line 1508, in doc pager(render_doc(thing, title, forceload)) File /home/milko/Среда/Python/trunk/Lib/pydoc.py, line 1503, in render_doc return title % desc + '\n\n' + text.document(object, name) File /home/milko/Среда/Python/trunk/Lib/pydoc.py, line 327, in document if inspect.isclass(object): return self.docclass(*args) File /home/milko/Среда/Python/trunk/Lib/pydoc.py, line 1216, in docclass lambda t: t[1] == 'static method') File /home/milko/Среда/Python/trunk/Lib/pydoc.py, line 1162, in spill name, mod, object)) File /home/milko/Среда/Python/trunk/Lib/pydoc.py, line 327, in document if inspect.isclass(object): return self.docclass(*args) TypeError: docclass() takes at most 4 arguments (5 given) Python 3.2a4+ (py3k:86836, Nov 27 2010, 18:35:01) [GCC 4.4.5] on linux2 Type help, copyright, credits or license for more information. class A: ... pass ... class B: ... attr = staticmethod(A) ... help(B) Traceback (most recent call last): File stdin, line 1, in module File /home/milko/Среда/Python/py3k/Lib/site.py, line 447, in __call__ return pydoc.help(*args, **kwds) File /home/milko/Среда/Python/py3k/Lib/pydoc.py, line 1713, in __call__ self.help(request) File /home/milko/Среда/Python/py3k/Lib/pydoc.py, line 1760, in help else: doc(request, 'Help on %s:') File /home/milko/Среда/Python/py3k/Lib/pydoc.py, line 1504, in doc pager(render_doc(thing, title, forceload)) File /home/milko/Среда/Python/py3k/Lib/pydoc.py, line 1499, in render_doc return title % desc + '\n\n' + text.document(object, name) File /home/milko/Среда/Python/py3k/Lib/pydoc.py, line 319, in document if inspect.isclass(object): return self.docclass(*args) File /home/milko/Среда/Python/py3k/Lib/pydoc.py, line 1214, in docclass lambda t: t[1] == 'static method') File /home/milko/Среда/Python/py3k/Lib/pydoc.py, line 1159, in spill name, mod, object)) File /home/milko/Среда/Python/py3k/Lib/pydoc.py, line 319, in document if inspect.isclass(object): return self.docclass(*args) TypeError: docclass() takes at most 4 positional arguments (5 given) -- components: Library (Lib) messages: 122535 nosy: milko.krachounov priority: normal severity: normal status: open title: help(cls1) breaks when cls1 has staticmethod(cls2) attribute versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10549 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10549] help(cls1) breaks when cls1 has staticmethod(cls2) attribute
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: Confirmed in py3k. -- assignee: - belopolsky nosy: +belopolsky stage: - needs patch type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10549 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10499] Modular interpolation in configparser
Łukasz Langa luk...@langa.pl added the comment: Patch reposted here for review: http://codereview.appspot.com/3309043/ -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10499 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10549] help(cls1) breaks when cls1 has staticmethod(cls2) attribute
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: The fix is simple: --- Lib/pydoc.py(revision 86824) +++ Lib/pydoc.py(working copy) @@ -1110,7 +1110,7 @@ result = result + self.section('FILE', file) return result -def docclass(self, object, name=None, mod=None): +def docclass(self, object, name=None, mod=None, *ignored): Produce text documentation for a given class object. realname = object.__name__ name = name or realname I think this is the right thing to do because HTMLDoc.docclass() has the following signature. def docclass(self, object, name=None, mod=None, funcs={}, classes={}, *ignored): -- stage: needs patch - unit test needed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10549 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10549] help(cls1) breaks when cls1 has staticmethod(cls2) attribute
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo, ncoghlan, ron_adam versions: -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10549 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10550] Windows: leak in test_concurrent_futures
New submission from Stefan Krah stefan-use...@bytereef.org: C:\Users\stefan\svn\py3k_64PCbuild\amd64\python_d.exe Lib\test\regrtest.py -R : test_concurrent_futures [1/1] test_concurrent_futures beginning 9 repetitions 123456789 . test_concurrent_futures leaked [6912, 6912, 6912, 6912] references, sum=27648 1 test failed: test_concurrent_futures [195615 refs] -- components: Extension Modules messages: 122539 nosy: skrah priority: normal severity: normal status: open title: Windows: leak in test_concurrent_futures type: resource usage versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10550 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10520] Build with --enable-shared fails
Łukasz Langa luk...@langa.pl added the comment: Roumen's patch fixes a regression where readline extension would fail to build on Mac OS X 10.6.5. -- nosy: +lukasz.langa resolution: fixed - stage: - commit review status: closed - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10520 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10550] Windows: leak in test_concurrent_futures
Stefan Krah stefan-use...@bytereef.org added the comment: posixmodule_listdir.patch fixes a leak in test_macpath. test_concurrent_futures still leaks. -- keywords: +patch Added file: http://bugs.python.org/file19839/posixmodule_listdir.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10550 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10551] mimetypes reading from registry in windows completely broken
New submission from Kovid Goyal ko...@kovidgoyal.net: Hi, I am the primary developer of calibre (http:/calibre-ebook.com) and yesterday I released an upgrade of calibre based on python 2.7. Here is a small sampling of all the diverse errors that my users experienced, related to reading mimetypes from the registry: 1. Permission denied if running from non privileged account Traceback (most recent call last): File site.py, line 103, in main File site.py, line 84, in run_entry_point File site-packages\calibre\__init__.py, line 31, in module File mimetypes.py, line 344, in add_type File mimetypes.py, line 355, in init File mimetypes.py, line 261, in read_windows_registry WindowsError: [Error 5] Acceso denegado (Access not allowed) The fix for this is to trap WindowsError and ignore it in mimetypes.py 2. Mishandling of encoding of registry entries Traceback (most recent call last): File site.py, line 103, in main File site.py, line 84, in run_entry_point File site-packages\calibre\__init__.py, line 31, in module File mimetypes.py, line 344, in add_type File mimetypes.py, line 355, in init File mimetypes.py, line 260, in read_windows_registry File mimetypes.py, line 250, in enum_types UnicodeDecodeError: 'utf8' codec can't decode byte 0xe0 in position 0: invalid continuation byte The fix for this is to change except UnicodeEncodeError to except ValueError 3. python -c import mimetypes; print mimetypes.guess_type('img.jpg') ('image/pjpeg', None) Where the output should have been (image/jpeg', None) The fix for this is to load the registry entries before the default entris defined in mimetypes.py Of course, IMHO, the best possible fix is to simply remove the reading of mimetypes from the registry. But that is up to whoever maintains this module. Duplicate (less comprehensive) tickets ont his isuue in your traceker already are: 9291, 10490, 104314 If the maintainer of this module is unable to fix these issues, let me know and I will submit a patch, either removing _winreg or fixing the issues individually. -- components: Library (Lib) messages: 122542 nosy: kovid priority: normal severity: normal status: open title: mimetypes reading from registry in windows completely broken versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10551 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10550] Windows: leak in test_concurrent_futures
Changes by Stefan Krah stefan-use...@bytereef.org: -- nosy: +bquinlan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10550 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10551] mimetypes reading from registry in windows completely broken
Ned Deily n...@acm.org added the comment: The first issue you note appears to be a duplicate of Issue10162, a fix for which should be available in the 2.7.1 maintenance release. The second issue appears to be a duplicate of Issue9291. Since that issue is still open, I suggest any further discussion be pursued there. You may want to add yourself to the nosy list of that issue. -- components: +Windows nosy: +brian.curtin, ned.deily resolution: - duplicate status: open - closed superseder: - mimetypes initialization fails on Windows because of non-Latin characters in registry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10551 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10541] regrtest.py -T broken
Antoine Pitrou pit...@free.fr added the comment: `make coverage` is fine, you just have to use the -m test.regrtest form when running the tests. -- nosy: +pitrou resolution: - invalid status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10541 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10541] regrtest.py -T broken
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: I would like to investigate this some more. In theory, regrtest should restore cwd before coverage results are written. -- status: pending - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10541 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10520] Build with --enable-shared fails
Barry A. Warsaw ba...@python.org added the comment: r86837 -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10520 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10537] OS X IDLE 2.7rc1 from 64-bit installer hangs when you paste something.
Ned Deily n...@acm.org added the comment: Regardless of the root cause, I really hate to see 2.7.1 go out with this unresolved. As it stands, IDLE was broken in the 2.7 64-bit OS X installer for 2.7 and, as it stands, is still broken. And whether it is an Apple Tk problem or not (which remains to be determined), there are workarounds that could be applied - like having a 32-bit-only IDLE built with Aqua Tk 8.4 as the 32-bit installers do. -- nosy: +benjamin.peterson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10537 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build
Terry J. Reedy tjre...@udel.edu added the comment: After reading the additional messages here and on a similar issue Alexander opened after this, I seem the point of wanting to make the difference between the two types of builds as transparent as sensibly possible. From that viewpoint, rejection of composed chars is not as bad because both types of builds act the same. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10521 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10552] Tools/unicode/gencodec.py error
New submission from Alexander Belopolsky belopol...@users.sourceforge.net: $ ../../python.exe gencodec.py MAPPINGS/VENDORS/MISC/ build/ converting APL-ISO-IR-68.TXT to build/apl_iso_ir_68.py and build/apl_iso_ir_68.mapping converting ATARIST.TXT to build/atarist.py and build/atarist.mapping converting CP1006.TXT to build/cp1006.py and build/cp1006.mapping converting CP424.TXT to build/cp424.py and build/cp424.mapping Traceback (most recent call last): File gencodec.py, line 421, in module convertdir(*sys.argv[1:]) File gencodec.py, line 391, in convertdir pymap(mappathname, map, dirprefix + codefile,name,comments) File gencodec.py, line 355, in pymap code = codegen(name,map,encodingname,comments) File gencodec.py, line 268, in codegen precisions=(4, 2)) File gencodec.py, line 152, in python_mapdef_code mappings = sorted(map.items()) TypeError: unorderable types: NoneType() int() It does appear to have been updated for 3.x: $ python2.7 gencodec.py MAPPINGS/VENDORS/MISC/ build/ Traceback (most recent call last): File gencodec.py, line 35, in module UNI_UNDEFINED = chr(0xFFFE) ValueError: chr() arg not in range(256) -- components: Demos and Tools messages: 122549 nosy: belopolsky, lemburg priority: normal severity: normal status: open title: Tools/unicode/gencodec.py error type: behavior versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10552 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7962] Demo and Tools need to be tested and pruned
Changes by Alexander Belopolsky belopol...@users.sourceforge.net: -- dependencies: +Tools/unicode/gencodec.py error ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7962 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9763] Crashes upon run after syntax error encountered in OSX 10.5.8
Ned Deily n...@acm.org added the comment: Adding the nosy list from Issue6628 where this problem was originally reported. What's interesting about this is that IDLE 2.x does not exhibit this behavior, AFAICT, when using the same Apple Tk 8.4. As there are other odd behaviors with IDLE 3.x on OS X, I want to investigate this further. -- nosy: +brian89, ronaldoussoren ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9763 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6628] IDLE freezes after encountering a syntax error
Ned Deily n...@acm.org added the comment: This issue was reported again in Issue9763; at the time, I overlooked your original report. As there is a more recent discussion of it over there, I am going to close this as a duplicate and add you to the nosy list there. -- resolution: - duplicate status: open - closed superseder: - Crashes upon run after syntax error encountered in OSX 10.5.8 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6628 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10553] Add optimize argument to builtin compile() and byte-compilation modules
New submission from Georg Brandl ge...@python.org: This patch adds an optimize parameter to compile(), as discussed in http://mail.python.org/pipermail/python-ideas/2010-November/008784.html. I also needed to introduce two new C APIs. Better naming suggestions are welcome. -- components: Library (Lib) files: compile-optimize.diff keywords: patch messages: 122552 nosy: georg.brandl, krisvale priority: normal severity: normal status: open title: Add optimize argument to builtin compile() and byte-compilation modules type: feature request versions: Python 3.2 Added file: http://bugs.python.org/file19840/compile-optimize.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10553 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10107] Quitting IDLE on Mac doesn't save unsaved code
Ned Deily n...@acm.org added the comment: Considering the discussion on the idle-dev list back in October about this issue, I think this low-risk, high-benefit fix should be going into all three upcoming releases. -- nosy: +benjamin.peterson, georg.brandl priority: high - critical ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10107 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10554] Context managerment support for subprocess.Popen
New submission from Éric Araujo mer...@netwok.org: I propose that __enter__ and __exit__ be added to subprocess.Popen. __enter__ returns self, __exit__ closes open file descriptors. __exit__ could also do the same checks that __del__ does (and which I don’t entirely understand. See also os.popen (os._wrap_close). -- components: Library (Lib) keywords: easy messages: 122554 nosy: eric.araujo priority: normal severity: normal stage: needs patch status: open title: Context managerment support for subprocess.Popen type: feature request versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10554 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10478] Ctrl-C locks up the interpreter
Antoine Pitrou pit...@free.fr added the comment: Here is a patch raising RuntimeError on reentrant calls to a buffered object. I haven't touched _pyio; I wonder how to do it without making it even slower. -- keywords: +patch Added file: http://bugs.python.org/file19841/reentrantio.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10478 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1731717] race condition in subprocess module
James Lamanna jlama...@gmail.com added the comment: stubbing out subprocess._cleanup does not work around the problem from this example on 2.6.5: import subprocess, signal subprocess._cleanup = lambda: None signal.signal(signal.SIGCLD, signal.SIG_IGN) subprocess.Popen(['echo','foo']).wait() ja...@hyla:~$ python tt.py foo Traceback (most recent call last): File tt.py, line 5, in module subprocess.Popen(['echo','foo']).wait() File /usr/lib/python2.6/subprocess.py, line 1170, in wait pid, sts = _eintr_retry_call(os.waitpid, self.pid, 0) File /usr/lib/python2.6/subprocess.py, line 465, in _eintr_retry_call return func(*args) OSError: [Errno 10] No child processes This bug still prevents subprocess from being used inside of a daemon where SIGCLD is being caught to reap zombie processes. -- nosy: +jlamanna ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1731717 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10478] Ctrl-C locks up the interpreter
Changes by Antoine Pitrou pit...@free.fr: -- stage: - patch review versions: +Python 2.7, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10478 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3548] subprocess.pipe function
Éric Araujo mer...@netwok.org added the comment: pipe.patch looks interesting to me. I would replace **kwargs with a keyword-only argument named stderr, since that’s the only key used. This requires more tests and docs. -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3548 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9264] trace.py documentation is incomplete
Terry J. Reedy tjre...@udel.edu added the comment: Éric, please feel free to commit (and even grab Assigned To:) when you feel patch is ready. You can do final review better than me. -- versions: -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9264 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10552] Tools/unicode/gencodec.py error
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: Attached patch addresses the issue by using -1 instead of None for missing codes. Comparison of generated encoding files to those in Lib/encodings shows only whitespace changes except one which appears to be a change on the unicode.org side: diff -b build/koi8_u.py ../../Lib/encodings/koi8_u.py 1c1 Python Character Mapping Codec koi8_u generated from 'MAPPINGS/VENDORS/MISC/KOI8-U.TXT' with gencodec.py. --- Python Character Mapping Codec koi8_u generated from 'python-mappings/KOI8-U.TXT' with gencodec.py. 221c221 '\u0491'# 0xAD - CYRILLIC SMALL LETTER GHE WITH UPTURN --- '\u0491' # 0xAD - CYRILLIC SMALL LETTER UKRAINIAN GHE WITH UPTURN 237c237 '\u0490'# 0xBD - CYRILLIC CAPITAL LETTER GHE WITH UPTURN --- '\u0490' # 0xBD - CYRILLIC CAPITAL LETTER UKRAINIAN GHE WITH UPTURN 308d307 -- keywords: +patch nosy: +loewis Added file: http://bugs.python.org/file19842/issue10552.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10552 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9509] argparse FileType raises ugly exception for missing file
Steven Bethard steven.beth...@gmail.com added the comment: Sorry, I was looking at the akira patch with the same date, where I was mainly worried about the modification of the except (TypeError, ValueError): block. Your patch doesn't do that, and looks fine. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9509 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10555] Fatal Python error: Interpreter not initialized (version mismatch?)
New submission from Anurag Chourasia anurag.choura...@gmail.com: Python extensions build on AIX 5.3 with GCC 4.2 fails. The configure command was as follows ./configure --enable-shared --disable-ipv6 --with-gcc=gcc CPPFLAGS=-I /opt/freeware/include -I /opt/freeware/include/readline -I /opt/freeware/include/ncurses LDFLAGS=-L. -L/usr/local/lib The error during the make step was as follows running build running build_ext ldd: /lib/libreadline.a: File is an archive. building dbm using ndbm INFO: Can't locate Tcl/Tk libs and/or headers building '_struct' extension creating build creating build/temp.aix-5.3-2.7 creating build/temp.aix-5.3-2.7/u01 creating build/temp.aix-5.3-2.7/u01/home creating build/temp.aix-5.3-2.7/u01/home/apli creating build/temp.aix-5.3-2.7/u01/home/apli/wm creating build/temp.aix-5.3-2.7/u01/home/apli/wm/GDD creating build/temp.aix-5.3-2.7/u01/home/apli/wm/GDD/Python-2.7 creating build/temp.aix-5.3-2.7/u01/home/apli/wm/GDD/Python-2.7/Modules gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -I/opt/freeware/include -I/opt/freeware/include/readline -I/opt/freeware/include/ncurses -I/usr/local/include -I/u01/home/apli/wm/GDD/Python-2.7/Include -I/u01/home/apli/wm/GDD/Python-2.7 -c /u01/home/apli/wm/GDD/Python-2.7/Modules/_struct.c -o build/temp.aix-5.3-2.7/u01/home/apli/wm/GDD/Python-2.7/Modules/_struct.o creating build/lib.aix-5.3-2.7 ./Modules/ld_so_aix gcc -pthread -bI:Modules/python.exp -L. -L/usr/local/lib build/temp.aix-5.3-2.7/u01/home/apli/wm/GDD/Python-2.7/Modules/_struct.o -L. -L/usr/local/lib -lpython2.7 -o build/lib.aix-5.3-2.7/_struct.so Fatal Python error: Interpreter not initialized (version mismatch?) make: 1254-059 The signal code from the last command is 6. The file build/lib.aix-5.3-2.7/_struct.so is present after this error. The error seems to be in importing the module that was just built. Here is the error message from the python executable that was built. root [zibal]% pwd /u01/home/apli/wm/GDD/Python-2.7 root [zibal]% which python ./python root [zibal]% python Python 2.7 (r27:82500, Nov 27 2010, 18:33:21) [GCC 4.2.4] on aix5 Type help, copyright, credits or license for more information. import struct Fatal Python error: Interpreter not initialized (version mismatch?) IOT/Abort trap(coredump) This is also an error in Version 2.6.6 I don't have any other conflicting python library that might cause this. -- components: Build messages: 122561 nosy: Anurag.Chourasia priority: normal severity: normal status: open title: Fatal Python error: Interpreter not initialized (version mismatch?) type: compile error versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10555 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10555] AIX 5.3 - GCC - Python 2.7 Shared Library Support - Fatal Python error: Interpreter not initialized (version mismatch?)
Changes by Anurag Chourasia anurag.choura...@gmail.com: -- title: Fatal Python error: Interpreter not initialized (version mismatch?) - AIX 5.3 - GCC - Python 2.7 Shared Library Support - Fatal Python error: Interpreter not initialized (version mismatch?) ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10555 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10518] Bring back callable()
Antoine Pitrou pit...@free.fr added the comment: It might be not obvious, but it's consistent with the check for other attributes. I don't know what attributes you're talking about, and there doesn't seem to be a lot of consistency there. Besides, being consistently obscure and hard to find is not the good type of consistency :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10518 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10518] Bring back callable()
Antoine Pitrou pit...@free.fr added the comment: Committed in r86842. -- resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10518 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10555] AIX 5.3 - GCC - Python 2.7 Shared Library Support - Fatal Python error: Interpreter not initialized (version mismatch?)
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +barry, skrah ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10555 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10542] Py_UNICODE_NEXT and other macros for surrogates
Marc-Andre Lemburg m...@egenix.com added the comment: I like the idea and thanks for putting work into this. Some comments: * when using macro variables, always put the variables in parens in the expansion; this avoids precedence issues, weird syntax errors, etc. - even if it may not be necessary * a function would be cleaner, but since this code is very performance sensitive, I'd opt for the macro version, unless someone can prove that a function would be just as fast in benchmarks * the macros should be documented in the unicodeobject.h header file and clearly mention that ptr and end should be side-effect free and that ptr must an lvalue * please use the faster bitmask operators for joining surrogates, i.e. ucs4 = high 0x03FF) 10) | (low 0x03FF)) + 0x0001); * the Py_UNICODE_JOIN_SURROGATES() macro should use Py_UCS4 as prefix since it returns Py_UCS4 values, i.e. Py_UCS4_JOIN_SURROGATES() * same for the Py_UNICODE_NEXT() macro, i.e. Py_UCS4_NEXT() * in order to make the macro easier to understand, please rename it to Py_UCS4_READ_CODE_POINT(); that's a little more typing, but still a lot less than without the macro :-) * this version should be slightly faster and is also easier to read: #define Py_UCS4_READ_CODE_POINT(ptr, end) \ ((Py_UNICODE_ISHIGHSURROGATE((ptr)[0]) \ (ptr) (end) \ Py_UNICODE_ISLOWSURROGATE((ptr)[1])) ? \ Py_UNICODE_JOIN_SURROGATES((ptr)++, (ptr)++) : \ (Py_UCS4)*(ptr)++) I haven't tested it, but you get the idea. BTW: You only focus on UCS2 builds. Please also make sure that these changes work on UCS4 builds, e.g. Py_UCS2_READ_CODE_POINT() will also work on UCS4 builds and join code points there. Note that UCS4 builds currently don't join surrogates, so a high and low surrogates appear as two code points, which they are, but given the experience with UCS2 builds, may not be what the user expects. So for the purpose of consistency we should be careful with auto-joining surrogates in UCS2. It does make sence for ord() and the various string methods, but should be done with care in other cases. In any case, we should clearly document where these macros are used and warn about the implications of using them in the wrong places. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10542 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10552] Tools/unicode/gencodec.py error
Marc-Andre Lemburg m...@egenix.com added the comment: Alexander Belopolsky wrote: Alexander Belopolsky belopol...@users.sourceforge.net added the comment: Attached patch addresses the issue by using -1 instead of None for missing codes. Comparison of generated encoding files to those in Lib/encodings shows only whitespace changes except one which appears to be a change on the unicode.org side: Please use a global constant instead of the literal -1, e.g. MISSING_CODE. Thanks. diff -b build/koi8_u.py ../../Lib/encodings/koi8_u.py 1c1 Python Character Mapping Codec koi8_u generated from 'MAPPINGS/VENDORS/MISC/KOI8-U.TXT' with gencodec.py. --- Python Character Mapping Codec koi8_u generated from 'python-mappings/KOI8-U.TXT' with gencodec.py. 221c221 '\u0491'# 0xAD - CYRILLIC SMALL LETTER GHE WITH UPTURN --- '\u0491' # 0xAD - CYRILLIC SMALL LETTER UKRAINIAN GHE WITH UPTURN 237c237 '\u0490'# 0xBD - CYRILLIC CAPITAL LETTER GHE WITH UPTURN --- '\u0490' # 0xBD - CYRILLIC CAPITAL LETTER UKRAINIAN GHE WITH UPTURN 308d307 That's just a comment and doesn't change the semantics of the codec. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10552 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10550] Windows: leak in test_concurrent_futures
Stefan Krah stefan-use...@bytereef.org added the comment: Committed posixmodule_listdir.patch in r86843. Unfortunately this is unrelated to the test_concurrent_futures leak. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10550 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10542] Py_UNICODE_NEXT and other macros for surrogates
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: On Sat, Nov 27, 2010 at 5:03 PM, Marc-Andre Lemburg rep...@bugs.python.org wrote: .. [I'll respond to skipped when I update the patch] In any case, we should clearly document where these macros are used and warn about the implications of using them in the wrong places. It may be best to start with _Py_UCS2_READ_CODE_POINT() (BTW, I like the name because it naturally lead to Py_UCS2_WRITE_CODE_POINT() counterpart.) The leading underscore will probably not stop early adopters from using it and we may get some user feedback if they ask to make these macros public. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10542 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10552] Tools/unicode/gencodec.py error
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10552 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10542] Py_UNICODE_NEXT and other macros for surrogates
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: On Sat, Nov 27, 2010 at 5:03 PM, Marc-Andre Lemburg rep...@bugs.python.org wrote: .. * same for the Py_UNICODE_NEXT() macro, i.e. Py_UCS4_NEXT() * in order to make the macro easier to understand, please rename it to Py_UCS4_READ_CODE_POINT(); that's a little more typing, but still a lot less than without the macro :-) I am not sure Py_UCS4_ prefix is right here. (I agree on *SURROGATE* methods.) The point of Py_UNICODE_NEXT(ptr, end) is that the pointers ptr and end are Py_UNICODE* and the macro expands to *p++ on wide builds. Maybe Py_UNICODE_NEXT_USC4? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10542 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7663] UCS4 build incorrectly translates cases for non-BMP code points
Ezio Melotti ezio.melo...@gmail.com added the comment: This is not yet fixed but will be addressed in #10521 and #10542. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7663 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10518] Bring back callable()
SilentGhost michael.mischurow+...@gmail.com added the comment: I thought PEP 3003 was quite unambiguous: This PEP proposes a temporary moratorium (suspension) of **all changes** to the Python language syntax, semantics, and built-ins for a period of at least two years from the release of Python 3.1. In particular, the moratorium would include Python 3.2 (to be released 18-24 months after 3.1) but allow Python 3.3 (assuming it is not released prematurely) to once again include language changes. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10518 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10542] Py_UNICODE_NEXT and other macros for surrogates
Marc-Andre Lemburg m...@egenix.com added the comment: Alexander Belopolsky wrote: Alexander Belopolsky belopol...@users.sourceforge.net added the comment: On Sat, Nov 27, 2010 at 5:03 PM, Marc-Andre Lemburg rep...@bugs.python.org wrote: .. * same for the Py_UNICODE_NEXT() macro, i.e. Py_UCS4_NEXT() * in order to make the macro easier to understand, please rename it to Py_UCS4_READ_CODE_POINT(); that's a little more typing, but still a lot less than without the macro :-) I am not sure Py_UCS4_ prefix is right here. (I agree on *SURROGATE* methods.) The point of Py_UNICODE_NEXT(ptr, end) is that the pointers ptr and end are Py_UNICODE* and the macro expands to *p++ on wide builds. Maybe Py_UNICODE_NEXT_USC4? The idea is that the first part refers to what the macro returns (Py_UCS4) and the read part of the name refers to moving a pointer across an array (any array of integers). Note that the macro can also work on Py_UCS4 arrays (even in UCS2 builds), so it's universal in that respect. Perhaps we should allow ord() to work on surrogates in UCS4 builds as well. That would reduce the number of surprises. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10542 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10518] Bring back callable()
Antoine Pitrou pit...@free.fr added the comment: Le samedi 27 novembre 2010 à 22:23 +, SilentGhost a écrit : SilentGhost michael.mischurow+...@gmail.com added the comment: I thought PEP 3003 was quite unambiguous: The stated goal of the moratorium is to make it easier for alternate implementations to catch up with the current language specification. Bringing back callable() doesn't go against this goal since they already have implemented it for 2.x. (not to mention that the implementation should be very simple) I wouldn't claim this is a authoritative interpretation but, if Guido doesn't oppose, I would take it for valid :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10518 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10542] Py_UNICODE_NEXT and other macros for surrogates
Eric Smith e...@trueblade.com added the comment: The idea is that the first part refers to what the macro returns (Py_UCS4) and the read part of the name refers to moving a pointer across an array (any array of integers). I thought the first part generally meant the type of the first parameter. Although I can go either way, especially if we add an underscore. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10542 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10518] Bring back callable()
SilentGhost michael.mischurow+...@gmail.com added the comment: I thought that moratorium meant Guido dis/approval is not applicable to the 3.2 Another listed change was help ease adoption of py3k. How's that helping? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10518 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10555] AIX 5.3 - GCC - Python 2.7 Shared Library Support - Fatal Python error: Interpreter not initialized (version mismatch?)
Stefan Krah stefan-use...@bytereef.org added the comment: Anurag, could you check out #941346 and see if there is anything that might help? I think this is AIX specific. -- nosy: +sable ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10555 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10518] Bring back callable()
Benjamin Peterson benja...@python.org added the comment: 2010/11/27 SilentGhost rep...@bugs.python.org: SilentGhost michael.mischurow+...@gmail.com added the comment: I thought that moratorium meant Guido dis/approval is not applicable to the 3.2 Another listed change was help ease adoption of py3k. How's that helping? By causing one less discontinuity. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10518 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10518] Bring back callable()
Antoine Pitrou pit...@free.fr added the comment: I thought that moratorium meant Guido dis/approval is not applicable to the 3.2 Guido can decide of everything: PEPs, etc. That's what BDFL means. So he can also decide of exceptions to the rules he decided on. (rules can have exception in any reasonable human society) Another listed change was help ease adoption of py3k. How's that helping? How's it not helping? I'm not sure what your general point or concern is. Do you have a real problem with callable() coming back or is it just a formal argument? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10518 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10542] Py_UNICODE_NEXT and other macros for surrogates
Ezio Melotti ezio.melo...@gmail.com added the comment: * the Py_UNICODE_JOIN_SURROGATES() macro should use Py_UCS4 as prefix since it returns Py_UCS4 values, i.e. Py_UCS4_JOIN_SURROGATES() * same for the Py_UNICODE_NEXT() macro, i.e. Py_UCS4_NEXT() I'm not so familiar with the prefix conventions, but wouldn't that lead users to think that this macro is for wide builds and that they have to use Py_UCS2_* macros for narrow builds? If these macros are supposed to abstract the build type maybe they should have a neutral prefix. (But if the conventions we use say otherwise I guess the best we can do is to document it properly). * in order to make the macro easier to understand, please rename it to Py_UCS4_READ_CODE_POINT(); that's a little more typing, but still a lot less than without the macro :-) The term code point is not entirely correct here. High and low surrogates are code points too. The right term should be 'scalar value' (but that might be confusing). The 'READ' bit sounds fine though, maybe 'READ_NEXT'? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10542 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10518] Bring back callable()
SilentGhost michael.mischurow+...@gmail.com added the comment: yes, my problem is that callable was removed and a way was shown how to do this check. The way which is consistent with the check for any other type (ABC). Now out of the blue, w/o any justification this way is going to be ignored, because ah, sure. I can't be bothered typing extra three characters and the old function is reintroduced. I don't like that we're heading into Perl's direction. that's all. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10518 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10547] FreeBSD: wrong value for LDSHARED in sysconfig
Stefan Krah stefan-use...@bytereef.org added the comment: Upgrading to critical, since I just verified that C extensions in general don't build on FreeBSD due to this issue. Sorry for bringing this up on the release day, it's a coincidence that I discovered it today... -- priority: normal - critical ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10547 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10518] Bring back callable()
Antoine Pitrou pit...@free.fr added the comment: yes, my problem is that callable was removed and a way was shown how to do this check. The way which is consistent with the check for any other type (ABC). ABCs are still the exception in Python, and duck typing is still the rule. I don't like that we're heading into Perl's direction. that's all. Well, please deal with it. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10518 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10518] Bring back callable()
SilentGhost michael.mischurow+...@gmail.com added the comment: ABCs are still the exception in Python, and duck typing is still the rule. Then why do we callable again? Don't worry, I'll deal with it. It's not like this whole discussion mattered. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10518 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10551] mimetypes reading from registry in windows completely broken
Kovid Goyal ko...@kovidgoyal.net added the comment: And what about the third issue? Allow me to elaborate: mimetypes are a relatively standard set of mappings from well known file extensions to MIME descriptors. Reading mimetype mappings from the registry, a location that is writable to by random programs the user may have installed on his machine, let alone malware, is a BAD idea. It leads to situations like asking for the mimetype of file.jpg and getting iage/pjpeg back. Or asking for the mimetype of file.png and getting image/x-png back. If you still consider it good to read mimetypes from the registry, at the very least, they should be read before the standard mimetype mappings defined in mimetypes.py are applied. That way at least for that set of mappings, users of python can be assured of sane query results. As it stands now, mimetypes.py is useless and to workaround the problem I essentially had to define the mimetype mappings for all the mimetypes my program knows about by hand. -- resolution: duplicate - status: closed - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10551 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10518] Bring back callable()
Antoine Pitrou pit...@free.fr added the comment: ABCs are still the exception in Python, and duck typing is still the rule. Then why do we callable again? Because the way __call__ is looked up means hasattr(x, __call__) is not the right answer. Otherwise there would be no point in bringing it back at all. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10518 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10552] Tools/unicode/gencodec.py error
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: Attached patch uses MISSING_CODE as Mark suggested. There are still errors apparently because parsecodes() may return either an int or a tuple. I think only mac encodings are affected, so I would like to commit the current patch before tackling this issue. $ ../../python.exe gencodec.py MAPPINGS/VENDORS/APPLE/ build/ mac_ converting ARABIC.TXT to build/mac_arabic.py and build/mac_arabic.mapping converting CELTIC.TXT to build/mac_celtic.py and build/mac_celtic.mapping converting CENTEURO.TXT to build/mac_centeuro.py and build/mac_centeuro.mapping converting CHINSIMP.TXT to build/mac_chinsimp.py and build/mac_chinsimp.mapping Traceback (most recent call last): File gencodec.py, line 424, in module convertdir(*sys.argv[1:]) File gencodec.py, line 394, in convertdir pymap(mappathname, map, dirprefix + codefile,name,comments) File gencodec.py, line 358, in pymap code = codegen(name,map,encodingname,comments) File gencodec.py, line 271, in codegen precisions=(4, 2)) File gencodec.py, line 155, in python_mapdef_code mappings = sorted(map.items()) TypeError: unorderable types: tuple() int() -- stage: - commit review Added file: http://bugs.python.org/file19843/issue10552a.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10552 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10552] Tools/unicode/gencodec.py error
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: Please ignore Makefile changes in the patch. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10552 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10551] mimetypes reading from registry in windows completely broken
Ned Deily n...@acm.org added the comment: (Sorry, I skipped over the third: this is one reason why one should not include multiple problems in one tracker issue.) As to your third point, a quick search of mimetypes in the bugtracker shows that looking in the Windows registry for mimetypes was a new feature in 2.7 and the upcoming 3.2 added by Issue4969. Adding the Windows maintainers and the Nosy List from that issue. -- nosy: +gagenellina, loewis, ocean-city, pitrou, tercero12, tim.golden superseder: mimetypes initialization fails on Windows because of non-Latin characters in registry - versions: +Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10551 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10542] Py_UNICODE_NEXT and other macros for surrogates
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: On Sat, Nov 27, 2010 at 5:41 PM, Ezio Melotti rep...@bugs.python.org wrote: Ezio Melotti ezio.melo...@gmail.com added the comment: * the Py_UNICODE_JOIN_SURROGATES() macro should use Py_UCS4 as prefix since it returns Py_UCS4 values, i.e. Py_UCS4_JOIN_SURROGATES() * same for the Py_UNICODE_NEXT() macro, i.e. Py_UCS4_NEXT() I'm not so familiar with the prefix conventions, but wouldn't that lead users to think that this macro is for wide builds and that they have to use Py_UCS2_* macros for narrow builds? If these macros are supposed to abstract the build type maybe they should have a neutral prefix. (But if the conventions we use say otherwise I guess the best we can do is to document it properly). When I was using the name, I did not think about argument type. Py_UNICODE_ is just the namespace prefix used by all macros in unicodeobject.h. Case in point: Py_UNICODE_ISALPHA() and family that take Py_UCS4. (I know, there is a historical reason at work here, but why fight it?) Functions use PyUnicode_ prefix and build specific functions use PyUnicodeUCSx_ prefix. As far as I can tell, there are no macros with Py_UCS4_ prefix. The choices I like in the order of preference are 1. Py_UNICODE_NEXT 2. Py_UNICODE_NEXT_UCS4 3. Py_UNICODE_READ_NEXT_UCS4 I can live with anything else, though. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10542 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10551] mimetypes read from the registry should not overwrite standard mime mappings
Kovid Goyal ko...@kovidgoyal.net added the comment: I apologize for the multiple issue in the ticket. To my mind they were all basically one issue, stemming from the decision to read mimetypes from the registry. Since there are other tickets for the first two issues, I'll change the summary for this issue to reflect only the third. -- title: mimetypes reading from registry in windows completely broken - mimetypes read from the registry should not overwrite standard mime mappings ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10551 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10556] test_zipimport_support mucks up with modules
New submission from Antoine Pitrou pit...@free.fr: This test failure is due to test_zipimport_support loading and unloading modules, which leads to them being reloaded. Then the ssl.CertificateError which is checked for by assertRaises isn't the same as the one raised by the module under test (I have printed the type names and ids below): $ ./python -E -bb -m test.regrtest test_http_cookies test_zipimport_support test_httplib [1/3] test_http_cookies [2/3] test_zipimport_support [3/3] test_httplib class 'ssl.CertificateError' 49243264 class 'ssl.CertificateError' 51134640 test test_httplib failed -- Traceback (most recent call last): File /home/antoine/py3k/__svn__/Lib/test/test_httplib.py, line 481, in test_local_bad_hostname h.request('GET', '/') File /home/antoine/py3k/__svn__/Lib/http/client.py, line 950, in request self._send_request(method, url, body, headers) File /home/antoine/py3k/__svn__/Lib/http/client.py, line 988, in _send_request self.endheaders(body) File /home/antoine/py3k/__svn__/Lib/http/client.py, line 946, in endheaders self._send_output(message_body) File /home/antoine/py3k/__svn__/Lib/http/client.py, line 791, in _send_output self.send(msg) File /home/antoine/py3k/__svn__/Lib/http/client.py, line 737, in send self.connect() File /home/antoine/py3k/__svn__/Lib/http/client.py, line 1096, in connect ssl.match_hostname(self.sock.getpeercert(), self.host) File /home/antoine/py3k/__svn__/Lib/ssl.py, line 142, in match_hostname % (hostname, dnsnames[0])) ssl.CertificateError: hostname 'localhost' doesn't match 'fakehostname' (witnessed in http://www.python.org/dev/buildbot/all/builders/AMD64%20Snow%20Leopard%203.x/builds/527/steps/test/logs/stdio ) -- components: Tests messages: 122590 nosy: brett.cannon, ncoghlan, pitrou priority: normal severity: normal stage: needs patch status: open title: test_zipimport_support mucks up with modules type: behavior versions: Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10556 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7663] narrow build incorrectly translates cases for non-BMP code points
Changes by Ezio Melotti ezio.melo...@gmail.com: -- title: UCS4 build incorrectly translates cases for non-BMP code points - narrow build incorrectly translates cases for non-BMP code points ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7663 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10542] Py_UNICODE_NEXT and other macros for surrogates
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: I suggest Py_UNICODE_ADVANCE() to avoid false suggestion that the iterator protocol is being used. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10542 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10542] Py_UNICODE_NEXT and other macros for surrogates
Antoine Pitrou pit...@free.fr added the comment: I suggest Py_UNICODE_ADVANCE() to avoid false suggestion that the iterator protocol is being used. You can't use the iterator protocol on a non-PyObject, and Py_UNICODE_* (as opposed to PyUnicode_*) suggests the macro operates on a raw array of code points. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10542 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10500] Palevo.DZ worm msix86 installer 3.x installer
Vil viligno...@gmail.com added the comment: http://www.python.org/ftp/python/3.1.2/python-3.1.2.msi it was this link on download page for msi windows x86 installer On Tue, Nov 23, 2010 at 6:03 AM, Martin v. Löwis rep...@bugs.python.orgwrote: Martin v. Löwis mar...@v.loewis.de added the comment: What file specifically did you download? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10500 ___ -- Added file: http://bugs.python.org/file19844/unnamed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10500 ___a href=http://www.python.org/ftp/python/3.1.2/python-3.1.2.msi;http://www.python.org/ftp/python/3.1.2/python-3.1.2.msi/abrbrit was this link on download page for msi windows x86 installerbrbrdiv class=gmail_quote On Tue, Nov 23, 2010 at 6:03 AM, Martin v. Löwis span dir=ltrlt;a href=mailto:rep...@bugs.python.org;rep...@bugs.python.org/agt;/span wrote:brblockquote class=gmail_quote style=margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex; br Martin v. Löwis lt;a href=mailto:mar...@v.loewis.de;mar...@v.loewis.de/agt; added the comment:br br What file specifically did you download?br br --br divdiv/divdiv class=h5br ___br Python tracker lt;a href=mailto:rep...@bugs.python.org;rep...@bugs.python.org/agt;br lt;a href=http://bugs.python.org/issue10500; target=_blankhttp://bugs.python.org/issue10500/agt;br ___br /div/div/blockquote/divbr ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com