There is no ./codespell.py about codespell HOT 18 CLOSED

Yes that's the next step, I should have time by next week

from codespell.

https://pypi.python.org/pypi/codespell/

from codespell.

I have verified locally that setuptools does indeed install a codespell.exe for Windows so just doing codespell works there with #136

from codespell.

It follows a more standard Python lib pattern to put it in bin. Really most people will / should probably now install via pip and thus just be able to do codespell.py directly

from codespell.

    copying build/scripts-3.4/codespell.py -> /home/scrutinizer/.pyenv/versions/3.4.1/bin
    changing mode of /home/scrutinizer/.pyenv/versions/3.4.1/bin/codespell.py to 775

is this normal? That I cant just run codespell.py but it seems only to be able able in /home/scrutinizer/.pyenv/versions/3.4.1/bin/codespell.py ?

from codespell.

most people will / should probably now install via pip and thus just be able to do codespell.py directly

...except now that pypi has been upgraded ( #101 ), pip will actually install the executable codespell instead of codespell.py

from codespell.

Argh, you're right. I guess we should revert to codespell.py for backward compatibility reasons

from codespell.

@lucasdemarchi do you agree we should change the name to bin/codespell.py instead of bin/codespell? I think it's necessary for backward compatibility.

from codespell.

Isn't it 'better' to have installed commands without the extension? (I assumed this change was deliberate)

from codespell.

Yeah it is better, but I'm worried about backward compatibility. For people who used to do codespell.py it won't work anymore. So I'm starting to think we should use the old name.

from codespell.

Please keep codespell file without file extension. It has been done this way for a long time. The convention has been changed in previous release and that is why we requested reverting it back to codespell.

from codespell.

Ahh okay, thanks @anatol

from codespell.

But the problem is that removing .py breaks the tool Windows, which relies on extensions to know how to execute a file. Could we have codespell.py for Windows, and just codespell elsewhere?

from codespell.

Should we just provide both, then?

from codespell.

Could we have codespell.py for Windows, and just codespell elsewhere?

I guess that's an option, too. I'll look and see what happens with binaries installed from other repos I work on. I know we have command-line utilities and AFAIK we don't do anything special for Windows. It's possible that they have just never worked there, I guess.

from codespell.

I guess that you can use setuptools to take care of it. This might be the best/simplest route. Someone want to give it a try?

from codespell.

Woohoo, great to see this issue fixed 👍 Any chance of a release on PyPi? ;)

from codespell.

Has the release been published?

from codespell.