FWIW I'm now -1 for this idea. Stronger integration with PyPI and packaging systems is much preferable. Python core public releases are no place for testing. On Sat, Jan 28, 2012 at 2:42 AM, Matt Joiner <anacrolix at gmail.com> wrote: > On Fri, Jan 27, 2012 at 12:26 PM, Alex <alex.gaynor at gmail.com> wrote: >> I think a significantly healthier process (in terms of maximizing feedback and >> getting something into it's best shape) is to let a project evolve naturally on >> PyPi and in the ecosystem, give feedback to it from an inclusion perspective, >> and then include it when it becomes ready on it's own merits. The counter >> argument to this is that putting it in the stdlib gets you signficantly more >> eyeballs (and hopefully more feedback, therefore), my only response to this is: >> if it doesn't get eyeballs on PyPi I don't think there's a great enough need to >> justify it in the stdlib. > > Strongly agree.
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