On Wed, Nov 7, 2012 at 8:46 AM, anatoly techtonik firstname.lastname@example.org:
On Tue, Nov 6, 2012 at 1:22 AM, Steven D'Aprano email@example.com wrote:
On 05/11/12 23:52, Ned Batchelder wrote:
Get everything the way you want it, and then propose it.
Also consider publishing it as a recipe on ActiveState, where many people will view it, use it, and offer feedback. This has many benefits:
You will gauge community interest;
Many eyeballs make bugs shallow;
You are providing a useful recipe that others can use, even if it doesn't get included in the std lib.
Some of the most useful parts of the std lib, like namedtuple, started life on ActiveState.
Why I don't use ActiveState:
- StackOverflow is much easier to access - just one click to login
with Google Account versus several clicks, data entry and copy/paste operations to remind the password on ActiveState - I want to login there with Python account 2. StackOverflow is problem search oriented - not recipe catalog oriented, which makes it better for solving problems, which I do more often than reading the recipe book (although I must admin when I was starting Python - the Cookbook from O'Reilly in CHM format was mega awesome) 3. I post the code as gists as it includes the notion of history, unlike ActiveState, which interface looks a little outdated - it was not obvious for me that recipes have history until today 4. Recipes are licensed, which is a too much of a burden for a snippet 5. ActiveState site makes it clear that it is ActiveState site - the 20% of my screen is taken by ActiveState header, so it looks like company site - not a site for community
Otherwise the idea of community recipe site is very nice.
https://gist.github.com/ works great too. But I believe we are a bit OT.