Re: No new features (was Re: [Python-Dev] Re: [Python-checkins] python/dist/src/Modules ossaudiodev.c, 1.35, 1.36)
Anthony Initially, I was inclined to be much less anal about the Anthony no-new-features thing. But since doing it, I've had a quite Anthony large number of people tell me how much they appreciate this Anthony approach - vendors, large companies with huge installed bases Anthony of Python, and also from people releasing software written in Anthony Python. Same here. People are amazed at work when I tell them I can just install a micro release without any breakage. Anthony I should also add that the above is really just policy as it's Anthony evolved - if people want to discuss this (am I being too Anthony strict?) I'm happy to talk about it. Current policy gets a big +1 from me. Skip ___ 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: No new features (was Re: [Python-Dev] Re: [Python-checkins]python/dist/src/Modules ossaudiodev.c, 1.35, 1.36)
G'day, From: Anthony Baxter [EMAIL PROTECTED] On Wednesday 09 March 2005 12:21, Greg Ward wrote: On 09 March 2005, Anthony Baxter said (privately): Thanks! I really want to keep the no-new-features thing going for as long as possible, pending any AoG (Acts of Guido), of course. [...] Initially, I was inclined to be much less anal about the no-new-features thing. But since doing it, I've had a quite large number of people tell me how much they appreciate this approach - vendors, large companies with huge installed bases of Python, and also from people releasing software written in Python. Very few people offer the counter argument as a general case - with the obvious exception that everyone has their just this one little backported feature, plase! (I'm the same - there's been times where I've had new features I'd have loved to see in a bugfix release, just so I could use them sooner). Just my 2c; I don't mind new features in minor releases, provided they meet the following two criteria; 1) Don't break the old API! The new features must be pure extensions that in no way change the old API. Any existing code should be un-effected in any way by the change. 2) The new features must be clearly documented as New in version X.Y.Z. This way people using these features will know the minium Python version required for their application. Any change that breaks rule 1) must be delayed until a major release. Any change that breaks rule 2) is a documentation bug that needs fixing. Donovan Baardahttp://minkirri.apana.org.au/~abo/ ___ 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
No new features (was Re: [Python-Dev] Re: [Python-checkins] python/dist/src/Modules ossaudiodev.c, 1.35, 1.36)
On 09 March 2005, Anthony Baxter said (privately): Thanks! I really want to keep the no-new-features thing going for as long as possible, pending any AoG (Acts of Guido), of course. Grumble. How do you feel about upgrading optparse to sync with Optik 1.5.1? I'm a bit embarassed that Python 2.4's optparse has __version__ == 1.5a2 because I didn't release Optik 1.5 in time. And yes, there were some tiny new features in 1.5 and a few more coming in 1.5.1: * SF patch #870807: allow users to specify integer option arguments in hexadecimal, octal, or binary with leading 0x, 0, or 0b (1.5 final). * SF feature #1050184: add 'append_const' action (patch by Andrea 'fwyzard' Bocci) (1.5 final). * Keep going if importing gettext fails (so optparse can be used in the Python build process) (1.5 final). * Fix so the 'merge' script works again (bugs spotted, and mostly fixed, by Andrea 'fwyzard' Bocci). (1.5.1) * SF bug #1145594: add 'finish()' method to OptionParser so applications can explicitly break reference cycles, making life easier for Python's garbage collector. (1.5.1) * SF feature #988126: add 'epilog' attribute to OptionParser (and constructor arg): paragraph of text to print after the main option help. (1.5.1) * Corrected French translation (po/optik/fr.po) (Laurent Laporte). (1.5.1) Every one of these is useful to someone, and none of them are even remotely destabilizing. But they all add functionality that would be present in 2.4.1 and not in 2.4. That doesn't bother me in the slightest, but I guess it bothers some people. I'd like to check this in for 2.4.1. But I won't if anyone says don't do it. Nor will I if no one else says do it. Burnt once... Greg -- Greg Ward [EMAIL PROTECTED] http://www.gerg.ca/ Any priest or shaman must be presumed guilty until proven innocent. ___ 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: No new features (was Re: [Python-Dev] Re: [Python-checkins] python/dist/src/Modules ossaudiodev.c, 1.35, 1.36)
On Tue, Mar 08, 2005, Greg Ward wrote: On 09 March 2005, Anthony Baxter said (privately): Thanks! I really want to keep the no-new-features thing going for as long as possible, pending any AoG (Acts of Guido), of course. Grumble. How do you feel about upgrading optparse to sync with Optik 1.5.1? I'm a bit embarassed that Python 2.4's optparse has __version__ == 1.5a2 because I didn't release Optik 1.5 in time. -1, sorry -- Aahz ([EMAIL PROTECTED]) * http://www.pythoncraft.com/ The joy of coding Python should be in seeing short, concise, readable classes that express a lot of action in a small amount of clear code -- not in reams of trivial code that bores the reader to death. --GvR ___ 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