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

Setup for Python 2/3 #4473

Merged
merged 3 commits into from Nov 5, 2013
Merged

Setup for Python 2/3 #4473

merged 3 commits into from Nov 5, 2013

Conversation

takluyver
Copy link
Member

This will almost certainly still have some problems, but it's at least working for me now.

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.

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}
Copy link
Member

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 ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems sensible. Done.

@Carreau
Copy link
Member

Carreau commented Nov 5, 2013

+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.
@minrk minrk merged commit b908251 into ipython:master Nov 5, 2013
@minrk
Copy link
Member

minrk commented Nov 5, 2013

Seems to work as expected here, merging.

@takluyver takluyver mentioned this pull request Nov 6, 2013
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants