-
-
Notifications
You must be signed in to change notification settings - Fork 106
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
Add entry point for python3 command #349
Comments
@conda-forge/core any thoughts on this? We were able to move a pip3 package through, but I know this one may be a little more contentious. |
How do you propose we build a python3.exe? copy |
Actually, I hadn't thought of that, and that sounds like a great easy idea!!! 100kB copy seems well worth it to me. Detailed motivationIn the cross referenced issue, I'm trying to get people going with
|
Any movement on this? There are conda packages (for me robostack/humble) that have scripts with python3 shebangs in the build chain which isn't just about changing user behaviour. Now I am manually adding a symlink, but that doesn't make for very portable environments
|
I still don't see why this is needed. |
For original source writers, It is very difficult to write "cross os" installation and running instructions.
The list kinda goes on. This really helps first time started get going with python |
So, you want to complicate the instructions with the following?
|
I would rather say:
In 2020, when I opened the issue, python2 was a real thing. so users accidentally having python2 was a real problem. I don't think there is a good "solution" to these problems, but I think that adding a |
The fact that this behaviour is different between linux and windows to me seems like enough of an argument to say the python3 alias should be included. Further there are packaged tools/scripts that use a python3 shebang, these simply do not work with the base python package (or worse call the global install) Why I pinged again today is I had to |
In Windows they use the pylauncher (what causes more headaches with conda environments) which emulates the |
Can you both please comment on python/cpython#99185 first? |
ok thank you for the constructive comment. I somewhat remember clashes between I'm going to try to test the new entry points before suggesting. I've been hit by similar bugs in the past in other packages. |
Issue:
On ubuntu, there is an entry point for both
python3
andpython3
.On windows,
python3
doesn't exist.Not sure about osx.
Could windows be added an entry point for the command
python3
so that we can reach a broader audiance with "fool proof" instructions.Ubuntu
Windows: (I deleted things in my roaming path between the two commands)
Environment (
conda list
):Details about
conda
and system (conda info
):The text was updated successfully, but these errors were encountered: