People:
I don't decide myself what to do in this case.
The Decimal module appeared in 2.4, and received just slight
modifications for 2.5. Since it appeared, a just download and use it
version was available for Python 2.3 users.
But for 2.6, it was fully renewed. Not only was updated to the
Decimal is a pretty stand alone module, and I'm absolutely sure that
just backporting the whole module and its testcases will fix a lot of
problems, and Py2.5 users will have new functionality, but is this ok?
Yes! We have guaranteed that spec updates are to be treated as bug fixes and
2007/10/2, Raymond Hettinger [EMAIL PROTECTED]:
Yes! We have guaranteed that spec updates are to be treated as bug fixes and
backported. This is especially important in this case
because other errors have been fixed and the test cases have grown.
Perfect! I'll backport it to 2.5... what
Yes! We have guaranteed that spec updates are to be treated as bug fixes
and backported. This is especially important in this
case
because other errors have been fixed and the test cases have grown.
Perfect! I'll backport it to 2.5... what about 2.4?
If there are any plans for another
If there are any plans for another 2.4 release, then yes; otherwise, why
bother.
Please don't make any functional changes to 2.4. There may be additional
releases, but (IMO) they should be security releases only, i.e. contain
no functional changes whatsoever (unless they fix a security issue).
On 10/2/07, Facundo Batista [EMAIL PROTECTED] wrote:
2007/10/2, Raymond Hettinger [EMAIL PROTECTED]:
Yes! We have guaranteed that spec updates are to be treated as bug
fixes and backported. This is especially important in this case
because other errors have been fixed and the test cases
2007/10/2, Mark Dickinson [EMAIL PROTECTED]:
difficulties. In particular, some cases of three-argument pow that
previously worked (giving arguably nonsensical results) will now raise an
exception. To be honest, I'd be quite surprised to find that *anyone* was
If previously it gave a
