Re: [Python-Dev] Tracker archeology
On Wed, Feb 11, 2009 at 12:46 AM, Stephen Thorne step...@thorne.id.au wrote: On 2009-02-10, Tarek Ziadé wrote: On Tue, Feb 10, 2009 at 2:23 PM, Daniel (ajax) Diniz aja...@gmail.com wrote: If anyone is interested in being added as nosy for any category of bugs, let me know and I'll do that as I scan the tracker. I'll take Distutils related issues, If you could look at a solution for http://bugs.python.org/issue1533164 I would be eternally grateful. ok, that would be the next one I am working on in that case, Regards Tarek ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python-acceleration instructions on ARM
On Feb, 11 2009 at 04:11:AM, Benjamin M. Schwartz bmsch...@fas.harvard.edu wrote: Brett Cannon wrote: On Tue, Feb 10, 2009 at 18:45, Benjamin Schwartz bmsch...@fas.harvard.eduwrote: ... According to ARM [4]: Jazelle RCT can be used to significantly reduce the code bloat associated with AOT and JIT compilation, making AOT technology viable on mass-market devices. It can also be used to support execution environments beyond Java, such as Microsoft .NET Compact Framework, Python and others. Jazelle RCT provides an excellent target for any run-time compilation technology, including JIT and AOT for .NET MSIL, Python and Perl as well as Java. ARM is working with leading software providers to enable solutions ready for market with Jazelle RCT. ... Question: ARM is specifically claiming that these instructions can be used to accelerate Python interpretation. Wow, really? One of the links below mention that? Yes. The quotes above from [4], as well as the white paper [6]. No specific data, just these broad claims. What would the process be to incorporate the use of ThumbEE instructions into CPython? Well, this all depends on how you try to integrate the instructions. If you hide it behind the macro or in a clean way that does not penalize skipping the instructions then you write a patch. But if this can't be done it would be better to maintain an external set of patches against trunk for this. Interesting. Sugar Labs will probably not attempt this if we would have to maintain a patched interpreter forever. However, I hope it will be possible to integrate into CPython in a manner that does not uglify the code or affect other architectures. Anyone else interested in ARM? ThumbEE support would benefit anyone running Python on recent ARM chips. Maybe we need to create a working group/project team/whatever. [4] http://www.arm.com/products/multimedia/java/jazelle_architecture.html [6] http://www.arm.com/pdfs/JazelleRCTWhitePaper_final1-0_.pdf It's not useful for CPython, since it's based on a loop which evaluates a bytecode at the time. You have to rewrite the virtual machine implementing a JIT compiler that generates Thumb-EE instructions. But it's a big effort, since ceval.c works in a completely different manner. I don't know if a form of JIT will be implemented in future CPython implementations, but if a step in this direction will be made, writing a back-end that uses Thumb-EE will be much easier. Cheers, Cesare ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python-acceleration instructions on ARM
Cesare Di Mauro wrote: It's not useful for CPython, since it's based on a loop which evaluates a bytecode at the time. You have to rewrite the virtual machine implementing a JIT compiler that generates Thumb-EE instructions. But it's a big effort, since ceval.c works in a completely different manner. I don't know if a form of JIT will be implemented in future CPython implementations, but if a step in this direction will be made, writing a back-end that uses Thumb-EE will be much easier. It is beginning to sound like PyPy may be a more appropriate platform for this experimentation than CPython. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python-acceleration instructions on ARM
Martin v. Löwis martin at v.loewis.de writes: - efficient array indexing: they give shift-and-index back to Thumb mode, for a shift by 2, allowing to index arrays with 4-byte elements in a single instruction (rather than requiring a separate multipy-by-four). Again useful for JIT of array access instructions, not applicable to Python - although it would be nice if the C compiler knew how to emit that. This could be used in PyTuple_GetItem and PyList_GetItem, no? (assuming Thumb has 4-byte pointers) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Daily documentation builds
On Tue, Feb 10, 2009 at 09:16:48PM -0800, Neal Norwitz wrote: I ran 2.6, 3.0, and 3.1 manually. 2.7 should get picked up on the next run. The problem is that regrtest.py -R hangs from time to time which caused the machine to run out of memory. Does anyone else have regrtest.py -R hang for them? Some tests were disabled to try to prevent the problem, but it still happens from time to time. It's also possible that tools/sphinx needs a manual 'svn update'. A recent change to sphinxext/pyspecific.py imports a new package, sphinx.builders. I had to do this to keep my source tree building the docs. --amk ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] IDLE reading IDLESTARTUP or PYTHONSTARTUP on restart
I have a patch for IDLE, but I've never submitted a patch before and not quite sure of the procedure, despite reading the guidelines at http://www.python.org/dev/patches/. But I'll be brave and persevere. The question I have at the moment is should I only submit the patch vs. 3.1 or also for 3.0? 2.7? 2.6? 2.5? The main thing the patch does is: modify the subprocess restart procedure so that it reloads whatever file, if any, was loaded when IDLE first started and looked for IDLESTARTUP then PYTHONSTARTUP environment variables. In addition: a -q option is added for starting IDLE on the command line to mean quiet, as with Emacs, e.g., to suppress loading of IDLESTARTUP or PYTHONSTARTUP The former effect of -s would now be the default, which is desirable so double-clicking an IDLE icon to start it will cause the startup file to run. -s is changed to take an argument that is an alternate startup file to use I am a bit concerned about changing -s to have a different meaning. Perhaps it's better to leave -s as an option that is simplhy superfluous and use a different letter for the alternate startup. Guidance on all of these would be greatly appreciated. The patch itself disturbs things in a half-dozen places, but in very minimal ways, so it's not quite as easy as saying add these three lines over here. (It was that simple until I started thinking about whether the restart should search for IDLESTARTUP/PYTHONSTARTUP again, and perhaps encounter a different file than IDLE did on startup [I think it shouldn't, but it's not a big deal either way] and if shouldn't, then whatever path was originally found has to be stored somewhere and used later. That led to the thinking behind the changes to the startup switches. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] python seg faults
I am running Python 2.5.4 compiled with gcc (Gentoo 4.3.2-r2 p1.5, pie-10.1.5) 4.3.2 My program uses python interface to two C modules namely libnids (pynids) and adns (adns-python). My program is written all in python. When I run my program it aborts. Here is the stack when that happens: #0 0x7f6cfdb79205 in raise () from /lib64/libc.so.6 #1 0x7f6cfdb7a723 in abort () from /lib64/libc.so.6 #2 0x7f6cfdbb4cf8 in ?? () from /lib64/libc.so.6 #3 0x7f6cfdbba468 in ?? () from /lib64/libc.so.6 #4 0x7f6cfdbbbfa6 in free () from /lib64/libc.so.6 #5 0x7f6cfe79dff2 in ?? () from /usr/lib/libpython2.5.so.1.0 #6 0x7f6cfe7fd736 in PyEval_EvalFrameEx () from /usr/lib/libpython2.5.so.1.0 #7 0x7f6cfe7fde7d in PyEval_EvalCodeEx () from /usr/lib/libpython2.5.so.1.0 #8 0x7f6cfe79f5ce in ?? () from /usr/lib/libpython2.5.so.1.0 #9 0x7f6cfe781e27 in PyObject_Call () from /usr/lib/libpython2.5.so.1.0 #10 0x7f6cfe782187 in ?? () from /usr/lib/libpython2.5.so.1.0 #11 0x7f6cfe7826c8 in PyObject_CallFunction () from /usr/lib/libpython2.5.so.1.0 #12 0x7f6cfd939b41 in callTcpFunc () from /usr/lib64/python2.5/site-packages/nidsmodule.so #13 0x7f6cfd93ebae in process_tcp (data=0x1a2f930 E, skblen=248) at tcp.c:805 #14 0x7f6cfd93bd7a in gen_ip_proc (data=0x1a2f930 E, skblen=248) at libnids.c:436 #15 0x7f6cfd93bbd8 in gen_ip_frag_proc (data=0x1a2f930 E, len=46) at libnids.c:388 #16 0x7f6cfd93b6a3 in call_ip_frag_procs (data=0x1a2f930, caplen=46) at libnids.c:198 #17 0x7f6cfd93ba05 in nids_pcap_handler (par=0x0, hdr=0x7fff06cc3500, data=0x1a2f922 ) at libnids.c:340 #18 0x7f6cfd7195d9 in pcap_offline_read () from /usr/lib/libpcap.so.1 #19 0x7f6cfd93c809 in nids_dispatch (cnt=1) at libnids.c:743 #20 0x7f6cfd939345 in nids_dispatch_exc () from /usr/lib64/python2.5/site-packages/nidsmodule.so #21 0x7f6cfd93a980 in pynids_run () from /usr/lib64/python2.5/site-packages/nidsmodule.so #22 0x7f6cfe7fcacd in PyEval_EvalFrameEx () from /usr/lib/libpython2.5.so.1.0 #23 0x7f6cfe7fde7d in PyEval_EvalCodeEx () from /usr/lib/libpython2.5.so.1.0 #24 0x7f6cfe7fe062 in PyEval_EvalCode () from /usr/lib/libpython2.5.so.1.0 #25 0x7f6cfe818601 in ?? () from /usr/lib/libpython2.5.so.1.0 #26 0x7f6cfe8186d6 in PyRun_FileExFlags () from /usr/lib/libpython2.5.so.1.0 #27 0x7f6cfe819c6d in PyRun_SimpleFileExFlags () from /usr/lib/libpython2.5.so.1.0 #28 0x7f6cfe82337a in Py_Main () from /usr/lib/libpython2.5.so.1.0 #29 0x7f6cfdb655c6 in __libc_start_main () from /lib64/libc.so.6 #30 0x00400789 in _start () When I run under valgrind I see a whole bunch of memory errors. Two of them are show below. ==26882== Thread 1: ==26882== Invalid free() / delete / delete[] ==26882==at 0x4C239FF: free (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so) ==26882==by 0x4E84FF1: (within /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4EE4735: PyEval_EvalFrameEx (in /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4EE4E7C: PyEval_EvalCodeEx (in /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4E865CD: (within /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4E68E26: PyObject_Call (in /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4E69186: (within /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4E696C7: PyObject_CallFunction (in /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x618FB40: callTcpFunc (in /usr/lib64/python2.5/site-packages/nidsmodule.so) ==26882==by 0x6194BAD: process_tcp (tcp.c:805) ==26882==by 0x6191D79: gen_ip_proc (libnids.c:436) ==26882==by 0x6191BD7: gen_ip_frag_proc (libnids.c:388) ==26882== Address 0x9195230 is 168,568 bytes inside a block of size 262,144 alloc'd ==26882==at 0x4C24CFE: malloc (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so) ==26882==by 0x4E9BEE8: PyObject_Malloc (in /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4F0B468: _PyObject_GC_Malloc (in /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4F0B55D: _PyObject_GC_NewVar (in /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4EAB313: PyTuple_New (in /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4EF9B28: (within /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4EFA0A0: (within /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4EF9B75: (within /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4EFA08A: (within /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4EFA755: PyMarshal_ReadObjectFromString (in /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4EFC272: PyMarshal_ReadLastObjectFromFile (in /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4EF453D: (within /usr/lib64/libpython2.5.so.1.0) ==26882== Invalid read of size 4 ==26882==at 0x4E9C20B: PyObject_Realloc (in /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4EA622E: _PyString_Resize (in /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4EDE458: (within /usr/lib64/libpython2.5.so.1.0) ==26882==by 0x4EE3128: PyEval_EvalFrameEx
Re: [Python-Dev] Daily documentation builds
On Wed, Feb 11, 2009 at 6:24 AM, A.M. Kuchling a...@amk.ca wrote: On Tue, Feb 10, 2009 at 09:16:48PM -0800, Neal Norwitz wrote: I ran 2.6, 3.0, and 3.1 manually. 2.7 should get picked up on the next run. The problem is that regrtest.py -R hangs from time to time which caused the machine to run out of memory. Does anyone else have regrtest.py -R hang for them? Some tests were disabled to try to prevent the problem, but it still happens from time to time. It's also possible that tools/sphinx needs a manual 'svn update'. A recent change to sphinxext/pyspecific.py imports a new package, sphinx.builders. I had to do this to keep my source tree building the docs. Ok, I'll take a look later. Misc/build.sh should be doing a make update which should fix most problems. There was one problem a while back I had to fix manually though. If you see ways to make Misc/build more robust, feel free to check in changes. The doc section is at the bottom of the file. n ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] IDLE reading IDLESTARTUP or PYTHONSTARTUP on restart
On Wed, Feb 11, 2009 at 1:45 PM, Mitchell L Model mlmli...@comcast.net wrote: I have a patch for IDLE, but I've never submitted a patch before and not quite sure of the procedure, despite reading the guidelines at http://www.python.org/dev/patches/. But I'll be brave and persevere. The question I have at the moment is should I only submit the patch vs. 3.1 or also for 3.0? 2.7? 2.6? 2.5? The guidelines listed above clearly state that patches should be sent relative to the current SVN tree. That would be 2.7, I guess. In addition, I would suggest uploading the patch to http://codereview.appspot.com which makes reviewing simpler. Perhaps, the guidelines page can mention this point. Guidance on all of these would be greatly appreciated. The patch itself disturbs things in a half-dozen places, but in very minimal ways, so it's The recommended way is to create a tracker issue (with or without patch) and send a mail here with the issue link and a brief description. That will allow interested people to check the issue and add comments. Thanks, Raghu ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python-acceleration instructions on ARM
Antoine Pitrou wrote: Martin v. Löwis martin at v.loewis.de writes: - efficient array indexing: they give shift-and-index back to Thumb mode, for a shift by 2, allowing to index arrays with 4-byte elements in a single instruction (rather than requiring a separate multipy-by-four). Again useful for JIT of array access instructions, not applicable to Python - although it would be nice if the C compiler knew how to emit that. This could be used in PyTuple_GetItem and PyList_GetItem, no? (assuming Thumb has 4-byte pointers) Yes - but it would require an assembly version of these functions; I'm skeptical that the savings would be measurable (given that there is also the type check and the range check). OTOH, PyTuple_GET_ITEM could probably be implemented as inline assembly. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python-acceleration instructions on ARM
At least IA32 and AMD64 have specific addressing modes where it's possibile to use a multiplying factor of 1, 2, 4 or 8 for the index register. I hope that compilers were smart enough to already used them. For x86, certainly (at least GCC does). For Thumb, certainly not: the compiler cannot assume that the code is in ThumbEE mode. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] python seg faults
So I am not sure where the error is. Any clue on where the bug possibly may be: adns-python, pynids or python? Or how I should I go about debugging this? This is out of scope for python-dev, but I give some clues anyway: - try finding out what kind of object is being released. Is it a good PyObject*? If so, what is its type? - try running Python in debug mode; this will add additional checks on memory sanity. HTH, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] python seg faults
Sushant Sinha wrote: I am running Python 2.5.4 compiled with gcc (Gentoo 4.3.2-r2 p1.5, pie-10.1.5) 4.3.2 My program uses python interface to two C modules namely libnids (pynids) and adns (adns-python). My program is written all in python. When I run my program it aborts. As Martin said, this is off-topic for python-dev until the problem has been demonstrated to be in the interpreter itself rather than in the extension modules (mis)use of the interpreter's C API. Until then, comp.lang.python or the user lists for those two C extension modules would be a more appropriate place to ask the question. Cheers, Nick. P.S. (From a quick glance at the stack trace, my initial bet would be on python-nids PCAP handling calling back in to the C API without reacquiring the GIL first) -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Tracker archeology
[Daniel (ajax) Diniz] Now will I'll start verifying, adding tests, updating or closing as needed the recently changed old issues, until I've taken a good look at these. Then, if there's still time left before Saturday, I'll focus on verifying/flagging more ancient ones. Thanks for your efforts. Raymond ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Python 3.0.1 planned for this Friday, Feb 13
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A quick reminder that I am planning to release Python 3.0.1 this Friday, February 13. Thanks to y'all's hard work, we have no showstopper bugs at the moment. The 3.0 buildbots look mostly clean and green. If we can keep it this way for about 24 hours, I will tag the branch at about 2300 UTC Thursday February 12 so that Martin can build the Windows installers on his Friday morning. Then Friday evening at about 2300 UTC, I will spin the tarballs and make the release. Cheers, Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSZNhLXEjvBPtnXfVAQKxoQP9HGUioYy3i0Z4glQfRevwJyiIvYqA1cF1 DKHpCn/8eJ/QXJ32Sfh/H2cASpDwkNNQLHrBOnzOPbe4M8ZJisg8bC27g+fTxckZ 5+yUJUTtRxk7/nDwWsS/DAWZ17VT9z8YN43XO2gGhcXw2YYl1Mi7VWvuZed9ojVL D7Gwy10S+s4= =RYa0 -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Tracker archeology
2009/2/11 Daniel (ajax) Diniz aja...@gmail.com Hi, Here's a status report about the digging. Thanks Benjamin, Antoine, Martin, Raymond, Guilherme, Georg, Brett, Mark and everyone else for helping :) Good: Many requested assignments: Thanks everyone that asked for bugs. If anyone else wants more, just let me know :) Old issues closed: ajaksu2 - 3 Everyone else - about 14 :) Checking and screening: 100 issues on the 'verify and close or update' queue (most of what is popping up as changed) Bad: Assignment mistakes: Two issues reassigned to Brett (from MvL and JvR) because I didn't see they were already assigned: http://bugs.python.org/issue1419652 PyImport_AppendInittab stores pointer to parameter http://bugs.python.org/issue616247 More documentation for the imp module Sorry about that :-/ No big deal. Over-spammig: Sorry, Georg! I only noticed all issues in the Documentation component are auto-assigned to you today. This meant dozens of unasked for assignments :-/ I think Georg at this point is the only auto-assignment. Now will I'll start verifying, adding tests, updating or closing as needed the recently changed old issues, until I've taken a good look at these. Then, if there's still time left before Saturday, I'll focus on verifying/flagging more ancient ones. One thing to keep an eye on for old issues, Daniel, is the Stage field. Setting that is nice for Bug Days as people can see what issues still need a test written or could use a review, etc. I have a doc I am writing up at http://docs.google.com/Doc?id=dg7fctr4_51cbt2vktw which outlines what the various Stage values should mean. Feedback from you and anybody else is welcome, although realize it is rough as I was not planning to make this public quite yet. during-bug-season-every-day-is-bug-day-ly y'rs, So true. =) -Brett ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] python seg faults
One more thing: There's a mailing list specifically for help with C extensions, c...@python.org -- Aahz (a...@pythoncraft.com) * http://www.pythoncraft.com/ Weinberg's Second Law: If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Tracker archeology
+1 on the cleanup: reading the bug description of http://bugs.python.org/issue1533164, this will also help Jython. Now I know why we see scenarios of package with setup.cfg with optimize=1: Indeed, this is a well-known issue. Many packages put an optimize=1 in their setup.cfg in order to solve it. Unfortunately that breaks the setup process on Jython, since we don't support -O. And unfortunately it's not as easy to ignore the flag either, this can then break in other ways. - Jim On Wed, Feb 11, 2009 at 2:08 AM, Tarek Ziadé ziade.ta...@gmail.com wrote: On Wed, Feb 11, 2009 at 12:46 AM, Stephen Thorne step...@thorne.id.au wrote: On 2009-02-10, Tarek Ziadé wrote: On Tue, Feb 10, 2009 at 2:23 PM, Daniel (ajax) Diniz aja...@gmail.com wrote: If anyone is interested in being added as nosy for any category of bugs, let me know and I'll do that as I scan the tracker. I'll take Distutils related issues, If you could look at a solution for http://bugs.python.org/issue1533164 I would be eternally grateful. ok, that would be the next one I am working on in that case, Regards Tarek ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/jbaker%40zyasoft.com -- Jim Baker jba...@zyasoft.com ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Tracker archeology
Jim Baker wrote: +1 on the cleanup: reading the bug description of http://bugs.python.org/issue1533164, this will also help Jython. Now I know why we see scenarios of package with setup.cfg with optimize=1: Indeed, this is a well-known issue. Many packages put an optimize=1 in their setup.cfg in order to solve it. Unfortunately that breaks the setup process on Jython, since we don't support -O. And unfortunately it's not as easy to ignore the flag either, this can then break in other ways. - Jim Add this comment to tracker if you want to be sure anyone reading it sees this ;-) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Tracker archeology
On Thu, Feb 12, 2009 at 4:11 AM, Daniel (ajax) Diniz aja...@gmail.com wrote: Now will I'll start verifying, adding tests, updating or closing as needed the recently changed old issues, until I've taken a good look at these. Then, if there's still time left before Saturday, I'll focus on verifying/flagging more ancient ones. during-bug-season-every-day-is-bug-day-ly y'rs, For urllib,urllib2 and urlparse related, please add me (orsenthil) to nosy list. I should already there. I shall test and provide patches. Thanks, Senthil ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
