Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

non-standard command names: setprojectdir, toggleglobalsitepackages #94

Open
thebjorn opened this issue Nov 18, 2017 · 2 comments
Open

Comments

@thebjorn
Copy link
Collaborator

It seems virtualenvwrapper-win has some commands renamed. setvirtualenvproject -> setprojectdir; toggsitepackages -> toggleglobalsitepackages.

from https://stackoverflow.com/questions/44611146/binding-virtualenv-to-project-using-setvirtualenvproject-command-doesnt-work-w/44613623#44613623

We should probably implement aliases for the "standard" names. It will help people following the linux documentation.

@xmedeko
Copy link

xmedeko commented Sep 21, 2018

Maybe instead of "aliases" the old names could be deprecated and later removed.

Anyway, I would welcome rather a simple command interface where possible, see my comment in #81.

@thebjorn
Copy link
Collaborator Author

@xmedeko I live in a world where backward compatibility is king, so unless there is a technical reason we cannot keep the existing command names I would never consider breaking other people's code for purely cosmetic reasons. I'm all for implementing the standard names and removing the non-standard names from the documentation, but deprecation should be limited to cases where we absolutely cannot keep existing functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants