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
Setup for Python 2/3 #4473
Merged
Merged
Setup for Python 2/3 #4473
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Scripts named ipython and ipython[23], etc. Neither distutils nor setuptools made this easy.
return [e % '' for e in ep] + [e % suffix for e in ep] | ||
|
||
script_src = """#!{executable} | ||
from {mod} import {func} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Want to add a comment that thoses script are autogenerated by setup.py
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems sensible. Done.
+1 :-) |
minrk
added a commit
that referenced
this pull request
Nov 5, 2013
update script generation in setup.py These changes: - Give us scripts called `ipython` and (`ipython2` or `ipython3`) for any installation. (and likewise for each of iptest, ipcontroller, etc.) - Add a new `setup.py symlink` target, to use instead of `develop`, which installs scripts and symlinks the library into site-packages, without using setuptools. - Removes the static script entry points - all our entry points are now automatically generated.
Seems to work as expected here, merging. |
Merged
mattvonrocketstein
pushed a commit
to mattvonrocketstein/ipython
that referenced
this pull request
Nov 3, 2014
update script generation in setup.py These changes: - Give us scripts called `ipython` and (`ipython2` or `ipython3`) for any installation. (and likewise for each of iptest, ipcontroller, etc.) - Add a new `setup.py symlink` target, to use instead of `develop`, which installs scripts and symlinks the library into site-packages, without using setuptools. - Removes the static script entry points - all our entry points are now automatically generated.
Carreau
added a commit
that referenced
this pull request
Feb 16, 2024
Apparently introduced in #4473 (over 10 years ago), undocumented.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will almost certainly still have some problems, but it's at least working for me now.
These changes:
ipython
and (ipython2
oripython3
) for any installation. (and likewise for each of iptest, ipcontroller, etc.)setup.py symlink
target, to use instead ofdevelop
, which installs scripts and symlinks the library into site-packages, without using setuptools.