[issue10516] Add list.clear() and list.copy()

Changes by Eli Bendersky : -- nosy: +eli.bendersky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

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

[issue10541] regrtest.py -T broken

Alexander Belopolsky 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 M

[issue9264] trace.py documentation is incomplete

Eli Bendersky added the comment: Éric, good idea - I'll do it. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue9264] trace.py documentation is incomplete

Eli Bendersky 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 Bla

[issue10242] unittest's assertItemsEqual() method makes too many assumptions about its input

Raymond Hettinger 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 _

[issue10544] yield expression inside generator expression does nothing

Raymond Hettinger added the comment: Hmm, what an interesting and unexpected side-effect of the efforts to hide the loop induction variable. -- nosy: +rhettinger ___ Python tracker ___

[issue10516] Add list.clear() and list.copy()

Eli Bendersky 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.

[issue10242] unittest's assertItemsEqual() method makes too many assumptions about its input

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

[issue10516] Add list.clear() and list.copy()

Xuanji Li 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 __

[issue10516] Add list.clear() and list.copy()

Eli Bendersky 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 l

[issue10516] Add list.clear() and list.copy()

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

[issue10542] Py_UNICODE_NEXT and other macros for surrogates

Marc-Andre Lemburg added the comment: Raymond Hettinger wrote: > > Raymond Hettinger added the comment: > > Mark, can you opine on this? Yes, I'll have a look later today. -- ___ Python tracker ___

[issue10383] test_os leaks under Windows

Stefan Krah 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 __

[issue10516] Add list.clear() and list.copy()

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

[issue9264] trace.py documentation is incomplete

Éric Araujo 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” will be give

[issue10516] Add list.clear() and list.copy()

Eli Bendersky 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 __

[issue9264] trace.py documentation is incomplete

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

[issue10516] Add list.clear() and list.copy()

Eli Bendersky 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 docume

[issue10516] Add list.clear() and list.copy()

Changes by Eli Bendersky : Removed file: http://bugs.python.org/file19834/unnamed ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue10547] FreeBSD: wrong value for LDSHARED in sysconfig

New submission from Stefan Krah : 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

[issue10547] FreeBSD: wrong value for LDSHARED in sysconfig

Changes by Stefan Krah : -- keywords: +buildbot -needs review, patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue9264] trace.py documentation is incomplete

Eli Bendersky 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/fi

[issue9509] argparse FileType raises ugly exception for missing file

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

[issue9509] argparse FileType raises ugly exception for missing file

SilentGhost 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

[issue9264] trace.py documentation is incomplete

Éric Araujo 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 w

[issue10548] Error in setUp not reported as expectedFailure (unittest)

New submission from Michael Foord : 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

[issue9264] trace.py documentation is incomplete

Eli Bendersky 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 is

[issue10516] Add list.clear() and list.copy()

Changes by Eli Bendersky : -- Removed message: http://bugs.python.org/msg122522 ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue9264] trace.py documentation is incomplete

Éric Araujo 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

[issue10531] write tilted text in turtle

Joe Metcalfe 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 turtl

[issue10531] write tilted text in turtle

Changes by Joe Metcalfe : -- versions: -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue4111] Add Systemtap/DTrace probes

Jesús Cea Avión 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

[issue10549] help(cls1) breaks when cls1 has staticmethod(cls2) attribute

New submission from Milko Krachounov : 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", "c

[issue10549] help(cls1) breaks when cls1 has staticmethod(cls2) attribute

Alexander Belopolsky added the comment: Confirmed in py3k. -- assignee: -> belopolsky nosy: +belopolsky stage: -> needs patch type: -> behavior ___ Python tracker ___ ___

[issue10499] Modular interpolation in configparser

Łukasz Langa added the comment: Patch reposted here for review: http://codereview.appspot.com/3309043/ -- ___ Python tracker ___ ___

[issue10549] help(cls1) breaks when cls1 has staticmethod(cls2) attribute

Alexander Belopolsky 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):

[issue10549] help(cls1) breaks when cls1 has staticmethod(cls2) attribute

Changes by Éric Araujo : -- nosy: +eric.araujo, ncoghlan, ron_adam versions: -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list

[issue10550] Windows: leak in test_concurrent_futures

New submission from Stefan Krah : C:\Users\stefan\svn\py3k_64>PCbuild\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 tes

[issue10520] Build with --enable-shared fails

Łukasz Langa 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

[issue10550] Windows: leak in test_concurrent_futures

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

[issue10551] mimetypes reading from registry in windows completely broken

New submission from Kovid Goyal : 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 registr

[issue10550] Windows: leak in test_concurrent_futures

Changes by Stefan Krah : -- nosy: +bquinlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue10551] mimetypes reading from registry in windows completely broken

Ned Deily 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 pu

[issue10541] regrtest.py -T broken

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

[issue10541] regrtest.py -T broken

Alexander Belopolsky 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 _

[issue10520] Build with --enable-shared fails

Barry A. Warsaw added the comment: r86837 -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue10537] OS X IDLE 2.7rc1 from 64-bit installer hangs when you paste something.

Ned Deily 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 det

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

Terry J. Reedy 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 c

[issue10552] Tools/unicode/gencodec.py error

New submission from Alexander Belopolsky : $ ../../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/cp100

[issue7962] Demo and Tools need to be tested and pruned

Changes by Alexander Belopolsky : -- dependencies: +Tools/unicode/gencodec.py error ___ Python tracker ___ ___ Python-bugs-list mailing

[issue9763] Crashes upon run after syntax error encountered in OSX 10.5.8

Ned Deily 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 wan

[issue6628] IDLE freezes after encountering a syntax error

Ned Deily 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 sta

[issue10553] Add optimize argument to builtin compile() and byte-compilation modules

New submission from Georg Brandl : This patch adds an "optimize" parameter to compile(), as discussed in . I also needed to introduce two new C APIs. Better naming suggestions are welcome. -- components: Library

[issue10107] Quitting IDLE on Mac doesn't save unsaved code

Ned Deily 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 __

[issue10554] Context managerment support for subprocess.Popen

New submission from Éric Araujo : 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_cl

[issue10478] Ctrl-C locks up the interpreter

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

[issue1731717] race condition in subprocess module

James Lamanna 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:~$ pytho

[issue10478] Ctrl-C locks up the interpreter

Changes by Antoine Pitrou : -- stage: -> patch review versions: +Python 2.7, Python 3.1 ___ Python tracker ___ ___ Python-bugs-list m

[issue3548] subprocess.pipe function

Éric Araujo 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

[issue9264] trace.py documentation is incomplete

Terry J. Reedy 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 __

[issue10552] Tools/unicode/gencodec.py error

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

[issue9509] argparse FileType raises ugly exception for missing file

Steven Bethard 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. -- ___ Pytho

[issue10555] Fatal Python error: Interpreter not initialized (version mismatch?)

New submission from Anurag Chourasia : 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" L

[issue10555] AIX 5.3 - GCC - Python 2.7 Shared Library Support - Fatal Python error: Interpreter not initialized (version mismatch?)

Changes by Anurag Chourasia : -- 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

[issue10518] Bring back callable()

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

[issue10518] Bring back callable()

Antoine Pitrou added the comment: Committed in r86842. -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue10555] AIX 5.3 - GCC - Python 2.7 Shared Library Support - Fatal Python error: Interpreter not initialized (version mismatch?)

Changes by Antoine Pitrou : -- nosy: +barry, skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue10542] Py_UNICODE_NEXT and other macros for surrogates

Marc-Andre Lemburg 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 f

[issue10552] Tools/unicode/gencodec.py error

Marc-Andre Lemburg added the comment: Alexander Belopolsky wrote: > > Alexander Belopolsky 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 cha

[issue10550] Windows: leak in test_concurrent_futures

Stefan Krah added the comment: Committed posixmodule_listdir.patch in r86843. Unfortunately this is unrelated to the test_concurrent_futures leak. -- ___ Python tracker ___

[issue10542] Py_UNICODE_NEXT and other macros for surrogates

Alexander Belopolsky added the comment: On Sat, Nov 27, 2010 at 5:03 PM, Marc-Andre Lemburg 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

[issue10552] Tools/unicode/gencodec.py error

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue10542] Py_UNICODE_NEXT and other macros for surrogates

Alexander Belopolsky added the comment: On Sat, Nov 27, 2010 at 5:03 PM, Marc-Andre Lemburg 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 typ

[issue7663] UCS4 build incorrectly translates cases for non-BMP code points

Ezio Melotti added the comment: This is not yet fixed but will be addressed in #10521 and #10542. -- ___ Python tracker ___ ___ Python

[issue10518] Bring back callable()

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

[issue10542] Py_UNICODE_NEXT and other macros for surrogates

Marc-Andre Lemburg added the comment: Alexander Belopolsky wrote: > > Alexander Belopolsky added the comment: > > On Sat, Nov 27, 2010 at 5:03 PM, Marc-Andre Lemburg > wrote: > .. >> * same for the Py_UNICODE_NEXT() macro, i.e. Py_UCS4_NEXT() >> >> * in order to make the macro easier to un

[issue10518] Bring back callable()

Antoine Pitrou added the comment: Le samedi 27 novembre 2010 à 22:23 +, SilentGhost a écrit : > SilentGhost 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 la

[issue10542] Py_UNICODE_NEXT and other macros for surrogates

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

[issue10518] Bring back callable()

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

[issue10555] AIX 5.3 - GCC - Python 2.7 Shared Library Support - Fatal Python error: Interpreter not initialized (version mismatch?)

Stefan Krah 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 ___

[issue10518] Bring back callable()

Benjamin Peterson added the comment: 2010/11/27 SilentGhost : > > SilentGhost 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 discontinuit

[issue10518] Bring back callable()

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

[issue10542] Py_UNICODE_NEXT and other macros for surrogates

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

[issue10518] Bring back callable()

SilentGhost 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

[issue10547] FreeBSD: wrong value for LDSHARED in sysconfig

Stefan Krah 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 __

[issue10518] Bring back callable()

Antoine Pitrou 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'

[issue10518] Bring back callable()

SilentGhost 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

[issue10551] mimetypes reading from registry in windows completely broken

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

[issue10518] Bring back callable()

Antoine Pitrou 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 bac

[issue10552] Tools/unicode/gencodec.py error

Alexander Belopolsky 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 i

[issue10552] Tools/unicode/gencodec.py error

Alexander Belopolsky added the comment: Please ignore Makefile changes in the patch. -- ___ Python tracker ___ ___ Python-bugs-list m

[issue10551] mimetypes reading from registry in windows completely broken

Ned Deily 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 feat

[issue10542] Py_UNICODE_NEXT and other macros for surrogates

Alexander Belopolsky added the comment: On Sat, Nov 27, 2010 at 5:41 PM, Ezio Melotti wrote: > > Ezio Melotti 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_U

[issue10551] mimetypes read from the registry should not overwrite standard mime mappings

Kovid Goyal 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 ref

[issue10556] test_zipimport_support mucks up with modules

New submission from Antoine Pitrou : 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 printe

[issue7663] narrow build incorrectly translates cases for non-BMP code points

Changes by Ezio Melotti : -- title: UCS4 build incorrectly translates cases for non-BMP code points -> narrow build incorrectly translates cases for non-BMP code points ___ Python tracker __

[issue10542] Py_UNICODE_NEXT and other macros for surrogates

Raymond Hettinger added the comment: I suggest Py_UNICODE_ADVANCE() to avoid false suggestion that the iterator protocol is being used. -- ___ Python tracker ___ __

[issue10542] Py_UNICODE_NEXT and other macros for surrogates

Antoine Pitrou 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.

[issue10500] Palevo.DZ worm msix86 installer 3.x installer

Vil 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 wrote: > > Martin v. Löwis added the comment: > > What file specifically did you download? > > ---

  1   2   >