Re: releasing & packaging vs. renaming

On 10/09/2011 11:40 AM, St�fan van der Walt wrote:
On Sun, Oct 9, 2011 at 2:08 AM, Nelle Varoquaux <nelle.varoquaux@gmail.com> wrote:
2011/10/9 St�fan van der Walt<stefan@sun.ac.za>
2011/10/8 St�fan van der Walt<stefan@sun.ac.za>:
On Sat, Oct 8, 2011 at 9:34 PM, Tony Yu<tsyu80@gmail.com> wrote:
Agreed: there's definitely a wide range of activity among the scikits. sklearn and statsmodels are probably a couple of the more active ones, so they'd be good examples to follow. And I also agree that changing the name sooner, rather than later, would be best. +1 Is there a preference between `skimage` and `skimg` ? Actually, `ski` is also available. Three letters--not too hard to type, doesn't sound awful (es-kay-eye for scikits image), and after all--it's just a module name :) I don't whether you'd take this in account, but it's quite hard to google. Googling sklearn directly links to the scikit-learn documentation. Same with statsmodels. Thanks, that's a valid concern. Seems like skimage is the top vote so far, then. Any other votes?
Don't know if this is a good argument but people might rather be googleing "python ski", which is easy to google. For this reason I am ambivalent between ski and skimage. Cheers, Andy

Don't know if this is a good argument but people might rather be googleing "python ski", which is easy to google. For this reason I am ambivalent between ski and skimage.
I'm more in favour of skimage (and having 'image' in the name of the package), but if we want something short and easy to google, 'skim' might be fun! Emma

On Sun, Oct 9, 2011 at 9:38 AM, Emmanuelle Gouillart < emmanuelle.gouillart@nsup.org> wrote:
Don't know if this is a good argument but people might rather be googleing "python ski", which is easy to google. For this reason I am ambivalent between ski and skimage.
I'm more in favour of skimage (and having 'image' in the name of the package), but if we want something short and easy to google, 'skim' might be fun!
Emma
I agree: having "image" in the name is preferable. If we start putting more interfaces to code in the top level module (right now, only functions from `util` are there) or automatically importing submodules (e.g. `io` would be a good candidate), then adopting/promoting the convention "import skimage as ski" would be nice (so the one import would give me `ski.img_as_float` and `ski.io.imread`). -Tony
participants (3)
-
Andreas Mueller
-
Emmanuelle Gouillart
-
Tony Yu