Re: [Python-Dev] error in Misc/NEWS
Raghuram Devarakonda [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] | There is an entry in Core and builtins section of Misc/NEWS: | | Bug #1722484: remove docstrings again when running with -OO.. | | The actual bug is 1722485. Incidentally, 1722484 appears to be spam. Sure enough. But it is another project -- and submitted anonymously. ___ 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] error in Misc/NEWS
Raghuram Devarakonda schrieb: There is an entry in Core and builtins section of Misc/NEWS: Bug #1722484: remove docstrings again when running with -OO.. The actual bug is 1722485. Incidentally, 1722484 appears to be spam. Fixed, thanks for spotting (you really read the commit logs thoroughly, don't you? ;) Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. ___ 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] Minor ConfigParser Change
On Friday 01 June 2007, BJörn Lindqvist wrote: Patches are applied once, but thousands of people read the code in the standard library each month. The standard library should be as readable as possible to make it as easy as possible to maintain. It is just good software development methodology. Rest assured, I understand your sentiment here, and am not personally against an occaissional clean-up. ConfigParser in particular is old and highly idiosyncratic. Many parts of the standard library are arcane and almost impossible to understand (see httplib for example) because refactoring changes are Not done. So if someone wants to improve the code why not let them? Changes in general are a source of risk; they have to be considered carefully. We've seen too many cases in which a change was thought to be safe, but broke something for someone. Avoiding style-only changes helps avoid introducing problems without being able to predict them; there are tests for ConfigParser, but it's hard to be sure every corner case has been covered. This is a general policy in the Python project, not simply my preference. I'd love to be able to say yes, the code is painful to read, let's make it nicer, but it's hard to say that without being able to say I'm sure it won't break anything for anybody. Python's too flexible for that to be easy. -Fred -- Fred L. Drake, Jr. fdrake at acm.org ___ 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] error in Misc/NEWS
On 6/1/07, Georg Brandl [EMAIL PROTECTED] wrote: Raghuram Devarakonda schrieb: There is an entry in Core and builtins section of Misc/NEWS: Bug #1722484: remove docstrings again when running with -OO.. The actual bug is 1722485. Incidentally, 1722484 appears to be spam. Fixed, thanks for spotting (you really read the commit logs thoroughly, don't you? ;) I was just scanning the file for the comment related to my patch (my first one, btw) when I spotted 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] failures in test_sqlite when entire test suite run
On 5/31/07, Brett Cannon [EMAIL PROTECTED] wrote: I have been getting failures from test_sqlite off the trunk when I run the entire test suite (as ``./python.exe Lib/test/regrtest.py``) with this error on OS X 10.4.9 and sqlite3 3.3.16: Traceback (most recent call last): File /Users/drifty/Dev/python/2.x/pristine/Lib/sqlite3/test/regression.py, line 29, in setUp self.con = sqlite.connect(:memory:) ProgrammingError: library routine called out of sequence When run in isolation it is fine. Anyone have a guess as to what is going on? Nevermind. It has started to pass again for me. -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
