[issue2262] Helping the compiler avoid memory references in PyEval_EvalFrameEx

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: We really could use an automated pybench runner on a dedicated machine driven by a buildbot feeding its results into a database so that we had a record of exactly when/what caused performance changes over time. This sounds remarkably like s

[issue2382] [Py3k] SyntaxError cursor shifted if multibyte character is in line.

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: > I tried to fix this problem, but I'm not sure how to fix this. Quick observation... /// // Possible Solution 1. Convert err->text to console compatible encoding (not to source encoding like in python2.x)

[issue2384] [Py3k] line number is wrong after encoding declaration

New submission from Hirokazu Yamamoto <[EMAIL PROTECTED]>: # This issue inherits from issue2301. If there is "# coding: " is in source code and coding is neigher utf-8 nor iso-8859-1, line number (tok->lineno) becomes wrong. Please look into Parser/tokenizer.c. In this case, tok->decoding_

[issue2385] run_setup can fail if the setup script uses __file__

New submission from Tarek Ziadé <[EMAIL PROTECTED]>: When calling run_setup, the execfile does not set the __file__ global variable, that is often used in setup.py modules (for instance to load a text file from the package to be used in the long_description) This patch adds this global variable

[issue2304] subprocess under windows fails to quote properly when shell=True

Tim Golden <[EMAIL PROTECTED]> added the comment: Updated patch against r61514. Test code now PEP8-compliant (I hope). New tests cover spaces in command and parameter with and without shell=True, both as simple command string and as list of command/args. Added file: http://bugs.python.org/file97

[issue2386] os.strerror missing/HAVE_STRERROR not defined

New submission from Ralf Schmitt <[EMAIL PROTECTED]>: os.strerror is missing on my 64 bit linux. HAVE_STRERROR is not defined in pyconfig.h. This has been broken in r61483. -- messages: 63908 nosy: brett.cannon, schmir severity: normal status: open title: os.strerror missing/HAVE_STRERRO

[issue2162] unittest.findTestCases undocumented

Virgil Dupras <[EMAIL PROTECTED]> added the comment: Can't we close this ticket? __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Uns

[issue2078] CSV Sniffer does not function properly on single column .csv files

Skip Montanaro <[EMAIL PROTECTED]> added the comment: What do you think the delimiter should be for this csv file? 43.4e12 147483648 47483648 What about this one? abcdef bcdefg cdefgh And this? abc8def bcd8efg cde8fgh If I force the sniffer to not allow digits or letters as delimiters I can

[issue2387] cStringIO and unicode

New submission from Virgil Dupras <[EMAIL PROTECTED]>: hsoft-dev:python hsoft$ python Python 2.5.1 (r251:54869, Apr 18 2007, 22:08:04) [GCC 4.0.1 (Apple Computer, Inc. build 5367)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from cStringIO import StringIO

[issue2320] Race condition in subprocess using stdin

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Thanks for clarifying, Jeffrey! I agree the Popen should be reentrant, since it's likey to be used that way. __ Tracker <[EMAIL PROTECTED]>

[issue2388] Compiler warnings when using UCS4

New submission from Benjamin Peterson <[EMAIL PROTECTED]>: Compiling Python with --enable-unicode=ucs4 yields some compiler warnings for unicodeobject.c: In file included from Objects/unicodeobject.c:7807: Objects/stringlib/string_format.h: In function 'do_conversion': Objects/stringlib/string_fo

[issue2388] Compiler warnings when using UCS4

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: What operating system/compiler? Both branches? What precise revisions? -- nosy: +loewis __ Tracker <[EMAIL PROTECTED]> __ ___

[issue2389] Array pickling exposes internal memory representation of elements

New submission from Hrvoje Nikšić <[EMAIL PROTECTED]>: It would seem that pickling arrays directly exposes the underlying machine words, making the pickle non-portable to platforms with different layout of array elements. The guts of array.__reduce__ look like this: if (array->ob_size >

[issue2388] Compiler warnings when using UCS4

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: This is MacOS 10.4, Apple gcc 4.0.1, and revision 61518. __ Tracker <[EMAIL PROTECTED]> __ ___ P

[issue984219] hotspot.stats.load is very slow

Virgil Dupras <[EMAIL PROTECTED]> added the comment: I had a 54 mb hotshot profile lying around, and it is indeed very long to load, so I ran a profiling session of hotshot.stats.load(MY_BIG_FILE) with python and stdlib of r61515, and here are the results (the resulting prof file is 27 mb):

[issue2388] Compiler warnings when using UCS4

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: There are similar warnings in formater_unicode.c: In file included from Python/formatter_unicode.c:13: Python/../Objects/stringlib/formatter.h: In function 'unicode__format__': Python/../Objects/stringlib/formatter.h:789: warning: format '%

[issue1506] func alloca inside ctypes lib needs #include on solaris

Thomas Heller <[EMAIL PROTECTED]> added the comment: I applied the patch to SVN trunk as rev 61520. It would probably be better to have a configure test for alloca.h. -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]>

[issue1399] XML codec

Changes by Sean Reifschneider <[EMAIL PROTECTED]>: -- resolution: -> rejected status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Pyth

[issue2386] os.strerror missing/HAVE_STRERROR not defined

Brett Cannon <[EMAIL PROTECTED]> added the comment: Fixed in revision 61523. Thanks for reminding me to remove those references, Ralf. -- assignee: -> brett.cannon resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]>

[issue2390] Merge 2.6 ACKS with 3.0 ACKS

New submission from Guido van Rossum <[EMAIL PROTECTED]>: Due to blocked merges etc. I expect that some names appearing in the 2.6 ACKS file aren't in the 3.0 ACKS file. And possible the other way around where backports are involved. I like this file to be as inclusive as possible (hey, my dad

[issue2392] Sean is testing tracker bug.

New submission from Sean Reifschneider <[EMAIL PROTECTED]>: Foo -- components: Demos and Tools messages: 63922 nosy: jafo severity: normal status: open title: Sean is testing tracker bug. versions: Python 2.5 __ Tracker <[EMAIL PROTECTED]>

[issue1598] unexpected response in imaplib

Scott Moser <[EMAIL PROTECTED]> added the comment: I can recreate this at the moment with the attached mail. I downloaded the mail using alpine's "Export". I don't know what other way I would have to get it. I have replaced many company names with XYZ and such, simply to anonymize the message

[issue1598] unexpected response in imaplib

Scott Moser <[EMAIL PROTECTED]> added the comment: This is the stderr from the test case above. Only modification is the mailbox is 'my-test'. Added file: http://bugs.python.org/file9728/failed-errorlog.txt __ Tracker <[EMAIL PROTECTED]>

[issue2393] Backport buffer interface in Python 3.0 to Python 2.6

Travis Oliphant <[EMAIL PROTECTED]> added the comment: Back-porting of the new buffer interface was done in r61491. This issue can be closed. __ Tracker <[EMAIL PROTECTED]> __

[issue1598] unexpected response in imaplib

Scott Moser <[EMAIL PROTECTED]> added the comment: > Can you provide the message or messages which cause the problem > when they are put in the IMAP server? See attached above > Can you also provide information on what IMAP server software > and version is being used? Its a lotus notes serv

[issue2393] Backport buffer interface in Python 3.0 to Python 2.6

New submission from Travis Oliphant <[EMAIL PROTECTED]>: Some (or all) of PEP 3118 should be backported to Python 2.6 because it does not require backward-incompatible changes and can assist in the transition to 3.0. This issue is to be sure that the buffer-interface portion of PEP 3118 is ba

[issue2394] Finish the memoryview object implementation

New submission from Travis Oliphant <[EMAIL PROTECTED]>: The memoryview object in Python 3.0 needs to be finished. There are a few methods that are not complete. In particular, the __getitem__ and __setitem__ functionality needs to be finished as well as the tolist() method. -- compone

[issue2395] struct module changes of PEP 3118

New submission from Travis Oliphant <[EMAIL PROTECTED]>: The additions to the struct module spelled out in PEP 3118 need to be implemented for Python 3.0 -- components: Library (Lib) messages: 63929 nosy: teoliphant severity: normal status: open title: struct module changes of PEP 3118 v

[issue2395] struct module changes of PEP 3118

Changes by Travis Oliphant <[EMAIL PROTECTED]>: -- type: -> behavior __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsub

[issue2396] Backport memoryview object to Python 2.6

New submission from Travis Oliphant <[EMAIL PROTECTED]>: The memoryview object in Python 2.6 would help in the transition to Python 3.0. It is a lower-priority and could wait until 2.7 if it doesn't get finished. -- components: Interpreter Core messages: 63930 nosy: teoliphant severity:

[issue2386] os.strerror missing/HAVE_STRERROR not defined

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: Attached patch fixes the problem. Note that the original os.strerror code was not standard compliant. See e.g. http://www.opengroup.org/onlinepubs/95399/functions/strerror.html -- keywords: +patch nosy: +belopolsky Added f

[issue2397] Backport 3.0 struct module changes to 2.6

New submission from Travis Oliphant <[EMAIL PROTECTED]>: The changes to the struct module in PEP 3118 should be backported to 2.6 as it is backward compatible and would smooth the transition to 3.0. It is lower priority and could wait until 2.7 -- components: Library (Lib) messages: 639

[issue2394] [Py3k] Finish the memoryview object implementation

Changes by Travis Oliphant <[EMAIL PROTECTED]>: -- title: Finish the memoryview object implementation -> [Py3k] Finish the memoryview object implementation __ Tracker <[EMAIL PROTECTED]>

[issue2395] [Py3k] struct module changes of PEP 3118

Changes by Travis Oliphant <[EMAIL PROTECTED]>: -- title: struct module changes of PEP 3118 -> [Py3k] struct module changes of PEP 3118 __ Tracker <[EMAIL PROTECTED]> __ _

[issue1518] Fast globals/builtins access (patch)

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Making sure I look at this at least once carefully before releasing. -- assignee: -> gvanrossum priority: -> critical __ Tracker <[EMAIL PROTECTED]> _

[issue2398] test_errno fails with unexpected error value EREMOTEIO

New submission from Andy Balaam <[EMAIL PROTECTED]>: Running test_errno on my 32-bit Ubuntu Gutsy machine gives me this: $ ./python Lib/test/test_errno.py test_for_improper_attributes (__main__.ErrnoAttributeTests) ... FAIL test_using_errorcode (__main__.ErrnoAttributeTests) ... ok test_attribut

[issue2303] isinstance is 4x as slow as in 2.5 because the common case raises

Thomas Heller <[EMAIL PROTECTED]> added the comment: Would it help to implement a default __instancecheck__ and __subclasscheck__ for object (or for type), that subclasses can override? -- nosy: +theller __ Tracker <[EMAIL PROTECTED]>

[issue2398] test_errno fails with unexpected error value EREMOTEIO

Brett Cannon <[EMAIL PROTECTED]> added the comment: Thanks for the patch, Andy, but I went ahead and fixed test_errno to only explicitly test errno values from Standard C. That way we are not constantly chasing our tail to support every errno value on every platform that Python runs on.

[issue2398] test_errno fails with unexpected error value EREMOTEIO

Andy Balaam <[EMAIL PROTECTED]> added the comment: Adding Brett Cannon since it looks like his checkin created the test which fails on my machine. Apologies if this is very bad etiquette. I couldn't find any guidelines about this in the developers' docs, but probably that's because I am incompe

[issue2398] test_errno fails with unexpected error value EREMOTEIO

Andy Balaam <[EMAIL PROTECTED]> added the comment: Woah! fast response, and what looks like a much more sensible fix. Thanks Brett. __ Tracker <[EMAIL PROTECTED]> __ __

[issue2390] Merge 2.6 ACKS with 3.0 ACKS

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file9732/merge_acks.py __ Tracker <[EMAIL PROTECTED]> __ ___ Python

[issue2399] Patches for Tools/msi

New submission from Travis Oliphant <[EMAIL PROTECTED]>: The attached patches add the following features to MSI building: * allow splitting into multiple CABs * prevent problem when data-base commits grow beyond a certain number * fix to handle all file names * change the way unique keys are

[issue1180] Option to ignore or substitute ~/.pydistutils.cfg

Changes by Paul Winkler <[EMAIL PROTECTED]>: -- nosy: +loewis __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe:

[issue2399] Patches for Tools/msi

Changes by Travis Oliphant <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file9734/msi.patch __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-

[issue2399] Patches for Tools/msi

Changes by Travis Oliphant <[EMAIL PROTECTED]>: -- nosy: +loewis __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscrib

[issue1581] xmlrpclib.ServerProxy() doesn't use x509 data

Bill Janssen <[EMAIL PROTECTED]> added the comment: Looking at this patch, I definitely agree with the need for documentation.And a test case which uses the SafeTransport class. But the patch itself also needs a bit more work. (It uses httplib.HTTPS underneath, and that needs more work, too

[issue2400] from .foo import * should work

New submission from Neal Norwitz <[EMAIL PROTECTED]>: Explicit relative imports using from .foo import * should work. http://mail.python.org/pipermail/python-3000/2008-March/012564.html -- components: Interpreter Core messages: 63942 nosy: nnorwitz priority: critical severity: normal st

[issue1251] ssl module doesn't support non-blocking handshakes

Bill Janssen <[EMAIL PROTECTED]> added the comment: I'm working on it. I'll close it when it's finished. __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bu

[issue1625] bz2.BZ2File doesn't support multiple streams

Changes by Sean Reifschneider <[EMAIL PROTECTED]>: -- assignee: -> niemeyer nosy: +niemeyer priority: -> normal __ Tracker <[EMAIL PROTECTED]> __

[issue1909] Backport: Mixing default keyword arguments with *args

Changes by Sean Reifschneider <[EMAIL PROTECTED]>: -- keywords: +26backport priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bu

[issue2387] cStringIO and unicode

Georg Brandl <[EMAIL PROTECTED]> added the comment: The 2.5.1 "fix" was determined to be too backwards-incompatible and since rolled back. The trunk behavior is "correct". Closing as rejected. -- nosy: +georg.brandl resolution: -> rejected status: open -> closed ___

[issue1745] Backport of PEP 3102 "keyword-only arguments" to 2.6

Changes by Eric Smith <[EMAIL PROTECTED]>: -- nosy: +eric.smith __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe

[issue1577] shutil.move() does not use os.rename() if dst is a directory

Sean Reifschneider <[EMAIL PROTECTED]> added the comment: After reviewing the discussion I'm going to accept this because: Guido seemed to me to say "figure it out among yourselves". We're talking about shutil, so mimicing the shell move (mv) semantics is not entirely unreasonable. The current

[issue2342] Comparing between disparate types should raise a Py3K warning

Steven Bethard <[EMAIL PROTECTED]> added the comment: Resolved in revision 61529. -- status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ __

[issue2373] Raise Py3K warnings for comparisons that changed

Steven Bethard <[EMAIL PROTECTED]> added the comment: Revision 61529 adds warnings for object, type, cell and dict comparisons. The code, method and slice warnings are still needed. __ Tracker <[EMAIL PROTECTED]>

[issue1975] signals in thread problem

Changes by Sean Reifschneider <[EMAIL PROTECTED]>: -- priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list

[issue2370] operator.{isCallable,sequenceIncludes} needs a fixer

Jeff Balogh <[EMAIL PROTECTED]> added the comment: I'll get this one. -- nosy: +jeff.balogh __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-li

[issue719888] tokenize module w/ coding cookie

Michael Foord <[EMAIL PROTECTED]> added the comment: Made quite extensive changes to tokenize.py (with tests) for Py3k. This migrates it to a 'bytes' API so that it can correctly decode Python source files following PEP-0263. -- nosy: +fuzzyman Added file: http://bugs.python.org/file9735

[issue2008] cookielib lacks FileCookieJar class for Safari

Changes by Sean Reifschneider <[EMAIL PROTECTED]>: -- assignee: -> loewis nosy: +loewis priority: -> normal __ Tracker <[EMAIL PROTECTED]> __

[issue2400] from .foo import * should work

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: More verbosely: The restriction should be removed; a SyntaxError shouldn't be raised, and import should handle it correctly. -- nosy: +benjamin.peterson __ Tracker <[EMAIL PROTECTED]>

[issue719888] tokenize module w/ coding cookie

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Michael, is the disappearance of the generate_tokens function in the new version of tokenize.py intentional? Tracker <[EMAIL PROTECTED]> __

[issue2303] isinstance is 4x as slow as in 2.5 because the common case raises

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Perhaps, though I'm not sure if that doesn't slow things down further due to the complicated protocol for calling it. Also, there's a recursion check in the built-in implementation. __ Tracker <[EMAIL PROTEC

[issue719888] tokenize module w/ coding cookie

Michael Foord <[EMAIL PROTECTED]> added the comment: That was 'by discussion with wiser heads than I'. The existing module has an old backwards compatibility interface called 'tokenize'. That can be deprecated in 2.6. As 'tokenize' is really the ideal name for the main entry point for the module

[issue2373] Raise Py3K warnings for comparisons that changed

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Your patch kicks up warnings in Objects/cellobject.c because cell_compare returns an int, your patch may return NULL. -- nosy: +benjamin.peterson __ Tracker <[EMAIL PROTECTED]>

[issue719888] tokenize module w/ coding cookie

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Is it worth keeping generate_tokens as an alias for tokenize, just to avoid gratuitous 2-to-3 breakage? Maybe not---I guess they're different beasts, in that one wants a string-valued iterator and the other wants a bytes-valued iterator. So

[issue2381] test_subprocess fails if your sys.executable is on a path with a space in it

Ralf Schmitt <[EMAIL PROTECTED]> added the comment: I can confirm this issue. 2 tests fail without this patch. please apply. here are the failing tests: == FAIL: test_args_string (test.test_subprocess.ProcessTestCase) --

[issue719888] tokenize module w/ coding cookie

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Sorry---ignore the last comment; if readline() doesn't supply bytes then the line.decode('ascii') will fail with an AttributeError. So there won't be silent failure. I'll try thinking first and posting later next time.

[issue2303] isinstance is 4x as slow as in 2.5 because the common case raises

Raymond Hettinger <[EMAIL PROTECTED]> added the comment: The attribute lookup cost can mostly be eliminated if __instancecheck__ were given a tp slot. -- nosy: +rhettinger __ Tracker <[EMAIL PROTECTED]> _

[issue719888] tokenize module w/ coding cookie

Trent Nelson <[EMAIL PROTECTED]> added the comment: Tested patch on Win x86/x64 2k8, XP & FreeBSD 6.2, +1. -- assignee: -> Trent.Nelson keywords: +patch Tracker <[EMAIL PROTECTED]> ___

[issue2373] Raise Py3K warnings for comparisons that changed

Steven Bethard <[EMAIL PROTECTED]> added the comment: On Tue, Mar 18, 2008 at 11:57 AM, Benjamin Peterson <[EMAIL PROTECTED]> wrote: > Benjamin Peterson <[EMAIL PROTECTED]> added the comment: > > Your patch kicks up warnings in Objects/cellobject.c because > cell_compare returns an int, your p

[issue2138] Add a factorial function

Mark Dickinson <[EMAIL PROTECTED]> added the comment: I'm not opposed to adding factorial somewhere, and it doesn't seem as though anyone else is actively opposed to factorial either. The problem is working out where best to put it. To my inexperienced eyes, it feels wrong to add it as an int/l

[issue2373] Raise Py3K warnings for comparisons that changed

Steven Bethard <[EMAIL PROTECTED]> added the comment: So I believe it should be returning -2 instead of NULL. Can someone verify that -2 means raise an exception for tp_compare? __ Tracker <[EMAIL PROTECTED]> ___

[issue2029] "python -m pydoc -g" fails

Changes by Sean Reifschneider <[EMAIL PROTECTED]>: -- assignee: -> ping nosy: +ping priority: -> normal type: -> behavior __ Tracker <[EMAIL PROTECTED]> __ _

[issue2052] Allow changing difflib._file_template character encoding.

Changes by Sean Reifschneider <[EMAIL PROTECTED]>: -- assignee: -> tim_one nosy: +tim_one priority: -> normal title: Lack of difflib.HtmlDiff unicode support -> Allow changing difflib._file_template character encoding. __ Tracker <[EMAIL PROTECTED]>

[issue2373] Raise Py3K warnings for comparisons that changed

Steven Bethard <[EMAIL PROTECTED]> added the comment: Ok, that warning should be gone now in trunk. __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-lis

[issue1747858] chown broken on 64bit

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: fixed in trunk r61540. I'm leaving this open until i backport it to release25-maint. -- resolution: -> remind versions: -Python 2.6 _ Tracker <[EMAIL PROTECTED]>

[issue1911] webbrowser.open firefox 3 issues

Changes by Michael Bishop <[EMAIL PROTECTED]>: -- type: -> behavior __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubs

[issue2401] Solaris: ctypes tests being skipped despite following #1516

New submission from Sean Reifschneider <[EMAIL PROTECTED]>: This is a break-out of the multi-issue #2048. Original poster Atro Tossavainen (atossava) reports:Building and testing on Solaris 8 on SPARC with Sun compilers: cc: Sun C 5.8 2005/10/13 CC: Sun C++ 5.8 2005/10/13 281 tests OK. 40 tests

[issue2401] Solaris: ctypes tests being skipped despite following #1516

Sean Reifschneider <[EMAIL PROTECTED]> added the comment: Martin v. Löwis (loewis) replies: What is the specific problem that you are reporting? I.e. what behavior did you expect instead? __ Tracker <[EMAIL PROTECTED]> _

[issue2401] Solaris: ctypes tests being skipped despite following #1516

Sean Reifschneider <[EMAIL PROTECTED]> added the comment: This is me: Martin: I believe the report is that the user followed #1516 but ctypes was not built, or at least the test was skipped. Assigning to theller, because that's whom #1516 is assigned to. -- assignee: loewis -> theller

[issue2138] Add a factorial function

Raymond Hettinger <[EMAIL PROTECTED]> added the comment: I prefer factorial as a method (like Ruby and Smalltalk). Given the usual notation (n!) or pronounciation (n factorial), it is natural to write this as: n.factorial(). Compared to numbits() and isqrt(), a factorial() method is more basi

[issue2048] IRIX: Seg-fault while building tests with gmake on test_xml_etree.

Sean Reifschneider <[EMAIL PROTECTED]> added the comment: Created issue #2401 for the Solaris problem. Repurposing this issue to just be the IRIX issue. -- nosy: +jafo priority: -> normal title: Python 2.5.1 woes on IRIX, Solaris -> IRIX: Seg-fault while building tests with gmake on t

[issue2392] Sean is testing tracker bug.

Changes by Martin v. Löwis <[EMAIL PROTECTED]>: __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue2392] Sean is testing tracker bug.

Changes by Martin v. Löwis <[EMAIL PROTECTED]>: -- resolution: -> invalid status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Python-b

[issue1747858] chown broken on 64bit

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: backported to 2.5 in r61542 and r61544. it'll go into py3k via the regular merges from trunk. The fix just changed the int -> long and 'ii' -> 'll' and added unit test coverage. The patch attached to this bug was rejected as too complex:

[issue2074] pprint._safe_repr() unsafe on ordering differently types objects with same str represenation

Sean Reifschneider <[EMAIL PROTECTED]> added the comment: I don't know if this is still relevent, if it is please provide a test that demonstrates it. I've checked the code and found that the code to be patched no longer exists. To me, it looks like it might be resolved. -- keywords: +

[issue2171] Add map, filter, zip to future_builtins

David Wolever <[EMAIL PROTECTED]> added the comment: Filter has been fixed in r61546. __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list

[issue2370] operator.{isCallable,sequenceIncludes} needs a fixer

Jeff Balogh <[EMAIL PROTECTED]> added the comment: Attaching a patch that operator.{isCallable,sequenceIncludes}, including tests. -- keywords: +patch Added file: http://bugs.python.org/file9736/issue2370.diff __ Tracker <[EMAIL PROTECTED]>

[issue2076] xmlrpclib closes connection after each call

Changes by Sean Reifschneider <[EMAIL PROTECTED]>: -- assignee: -> effbot nosy: +effbot priority: -> normal type: -> feature request __ Tracker <[EMAIL PROTECTED]> __ __

[issue2403] Add figleaf coverage metrics

New submission from Jerry Seutter <[EMAIL PROTECTED]>: This issue adds support for figleaf unit test coverage information. The diffs apply against trunk -- components: Tests files: README.patch keywords: patch, patch messages: 63975 nosy: jseutter priority: low severity: normal status:

[issue2403] Add figleaf coverage metrics

Changes by Jerry Seutter <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file9738/coverage.zip __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs

[issue2077] Interpreter crash on shutdown

Changes by Sean Reifschneider <[EMAIL PROTECTED]>: -- priority: -> high __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Un

[issue2403] Add figleaf coverage metrics

Jerry Seutter <[EMAIL PROTECTED]> added the comment: To test: 1. Unzip the zipfile in the base python directory. The zipfile will create Tools/coverage*. 2. cd Tools; patch -p0 README.patch 3. cd coverage 4. ../../python.exe coverage.py The script will download figleaf, then run regrtest.py.

[issue2090] __import__ with fromlist=[''] causes double initialization of modules

Changes by Sean Reifschneider <[EMAIL PROTECTED]>: -- assignee: -> brett.cannon nosy: +brett.cannon priority: -> normal __ Tracker <[EMAIL PROTECTED]> __

[issue2404] Backport ctypes support for buffer protocol to Python 2.6 (ref issue1971)

New submission from Travis Oliphant <[EMAIL PROTECTED]>: The ctypes object will support the PEP 3118 buffer protocol. This support can be back-ported to Python 2.6 -- messages: 63977 nosy: teoliphant severity: normal status: open title: Backport ctypes support for buffer protocol to Pyt

[issue2404] Backport ctypes support for buffer protocol to Python 2.6 (ref issue1971)

Changes by Travis Oliphant <[EMAIL PROTECTED]>: -- assignee: -> theller components: +ctypes nosy: +theller type: -> behavior versions: +Python 2.6 __ Tracker <[EMAIL PROTECTED]> __ _

[issue2100] unit test UnicodeWarning

Changes by Sean Reifschneider <[EMAIL PROTECTED]>: -- assignee: -> mhammond nosy: +mhammond priority: -> normal __ Tracker <[EMAIL PROTECTED]> __

[issue2073] asynchat push always sends 512 bytes (ignoring ac_out_buffer_size)

Changes by Sean Reifschneider <[EMAIL PROTECTED]>: -- assignee: -> gvanrossum nosy: +gvanrossum priority: -> normal __ Tracker <[EMAIL PROTECTED]> __

[issue2405] Drop w9xpopen and all dependencies

New submission from Trent Nelson <[EMAIL PROTECTED]>: Python 2.6+ drops support for Windows 95/98, which removes the need for w9xpopen. Get rid of the module and all dependencies (such as in the .msi). -- assignee: Trent.Nelson components: Build messages: 63978 nosy: Trent.Nelson severi

[issue2403] Add figleaf coverage metrics

Neal Norwitz <[EMAIL PROTECTED]> added the comment: Thanks for the patch. It would be nice to get more instrumentation like coverage, performance, etc. Here are some things I noticed while reviewing the patch: * This won't work on unix other than OSX. Can you change ../../python.exe to sys.e

  1   2   >