module naming conventions

Terry Reedy tjreedy at udel.edu
Wed Jan 16 21:16:40 CET 2008


"Tobiah" <toby at tobiah.org> wrote in message 
news:478d113a$0$26041$88260bb3 at free.teranews.com...
|
| > Release your package as free software on the Cheeseshop
| > <URL:http://cheeseshop.python.org/>. If the name you want is already
| > taken, pick one that will help users distinguish yours from the
| > existing one.
| >
|
| I like this idea.  I developed a library with a name that got
| a couple of obscure software related hits on Google.  I checked
| sourceforge, and found that the name was available, so I stuck
| my flag in the dirt.
|
| It was a python module, so I suppose I will have to look into
| the cheeseshop.  Is that as open as sourceforge, or is it only
| for mature, sophisticated modules?

Look at the cheeseshop page, but I would say that 'mature' and
'sophisticated' are too high a bar.  'Potentially useful and 
not-known-to-be-buggy'
should be more like it. 






More information about the Python-list mailing list