> [Ivan Judson] >> What's needs to be done to possibly get PEP754 (fpconst) to move >> ahead and perhaps go into 2.4? This one seems to have slipped through the cracks. I haven't heard from the author lately; hopefully he hasn't lost interest. In any case, an active champion is needed for progress. Tim Peters wrote: > + The implementation URL in the PEP no longer resolves, so that > needs to be fixed. A Google search resulted in: <http://www.analytics.washington.edu/statcomp/projects/rzope/fpconst/> I've updated the PEP. > + Last time I saw it, fpconst.py had a Pfizer copyright and > license, which makes headaches for everyone. > > + It needs docs. > > + It needs a test suite. > > + Guido has to Pronounce on it. Is Guido's waiting for your (Tim's) recommendation? Guido wrote, "David, I'll leave the review of this PEP entirely to Tim, if you don't mind". At the time (2003-10-05) Tim wrote: Guido and I have discussed this in email today. We're both favorable. It may get buried under feature creep, though (that is, if the PEP is good so far as it goes, it may be necessary to make it go farther, addressing some of the other problems mentioned-- but not solved --by the PEP). Gregory Warnes (the PEP author) had a few questions the next day (2003-10-06); I wasn't copied on replies if any. Shall I forward Gregory's messages to you? I'm copying Gregory on this message. -- David Goodger <http://starship.python.net/~goodger> Python Enhancement Proposal (PEP) Editor <http://www.python.org/peps/> (Please cc: all PEP correspondence to <peps at python.org>.)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4