Patch / Bug Summary
___
Patches : 303 open ( -5) / 2764 closed ( +9) / 3067 total ( +4)
Bugs: 849 open (+11) / 4837 closed ( +3) / 5686 total (+14)
RFE : 169 open ( +1) / 148 closed ( +0) / 317 total ( +1)
New / Reopened Patches
__
New fpcon
Warnes, Gregory R wrote:
What else needs to be done to allow fpconst to go into the Python library?
See PEP 1. First, the PEP must be Accepted.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/pyt
[Peter Harris]
> I look forward to the day when I can just use it.
You PEP is marked as final. The code has been checked in to CVS and
will be in Py2.5.
Congrats,
Raymond Hettinger
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyt
Peter Harris <[EMAIL PROTECTED]> wrote:
> However, I sympathise with anyone who feels unhappy about a new module
> just for what amounts to one function.
Well, since it seems that the emphasis in Python development is now
moving more towards expanding the standard library, a module that has
only o
Overall, I have no major objections to the PEP or the patch. Before it
goes in on auto-pilot, it would be darned nice if the proponents said
that they've found it helpful in real code and that they are satisfied
with the timings.
I guess "darned nice" is the best you can hope for. Not sure i
[After a long delay, the thread continues]
Hi All,
I'm pushing ahead on the tasks necessary to add the 'fcponst' module
described in PEP 754: IEEE 754 Floating Point Special Values.
Per http://www.python.org/psf/contrib, I've
- Changed the license to the Apache License, Version 2.0
- Just
Samuele Pedroni wrote:
Nick Coghlan wrote:
The initial suggestion was to provide a __get__ method on partial
objects, which forces the insertion of the reference to self at the
beginning of the argument list instead of at the end:
def __get__(self, obj, type=None):
if obj is None:
