Hi!
Don't now if always, or in the last few months where I've been
following the issues more closely, but I found that are appearing a
lot of small RFEs in the tracker.
These normally are small but not trivial things. In most cases when I
read them I think "Mmm, yes... it won't hurt to have it, but it's not
so important, and definitively not my itch to scratch". See, for
example, this [1] one, that ask for a factorial method in the
integers.
Normally these RFEs stay there for a long time, unless they're clearly
negative, because they don't raise any discussion.
OTOH, we have a PEP for feature requests [2]. I quote part of it:
"""
This PEP was created to allow us to close bug reports that are really
feature requests. Marked as Open, they distract from the list of real
bugs (which should ideally be less than a page). Marked as Closed, they
tend to be forgotten. The procedure now is: if a bug report is really
a feature request, add the feature request to this PEP; mark the bug as
"feature request", "later", and "closed"; and add a comment to the bug
saying that this is the case (mentioning the PEP explicitly).
"""
This is still valid? Should we start moving RFEs to this PEP and
closing their issues in the tracker?
Or should we try to get more discussion regarding these RFEs? Maybe,
for example, a weekly digest where the latests RFEs added are sent to
python-dev, so we can actually say "no way" and close them, or say
"nice" and *then* moving them to the PEP (this has the risk of nobody
saying anything, and to stay in the same position as before).
What do you think? Opinions?
Thank you very much!
Regards,
[1] http://bugs.python.org/issue2138
[2] http://www.python.org/dev/peps/pep-0042/
--
. Facundo
Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
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