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

Pip install setup docs #2020

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Pip install setup docs #2020

wants to merge 4 commits into from

Conversation

richafrank
Copy link
Member

@coveralls
Copy link

coveralls commented Nov 21, 2017

Coverage Status

Coverage remained the same at 87.341% when pulling 1a68e56 on pip-install-setup-docs into 079ea3d on master.

@@ -33,51 +33,6 @@
import versioneer


class LazyBuildExtCommandClass(dict):
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we check for numpy/Cython being installed and fail with a clear error here if they're not?

Copy link
Contributor

Choose a reason for hiding this comment

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

We should remove the setup_requires for numpy/Cython as well, since they're the main thing that causes breakage.

Copy link
Member Author

Choose a reason for hiding this comment

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

Hmm, as it currently is, setup.py develop is broken. Will need to dig into it if we want to remove even more.

Copy link
Member Author

Choose a reason for hiding this comment

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

Ok, updated.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.07%) to 87.276% when pulling 25e2150 on pip-install-setup-docs into 079ea3d on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 87.341% when pulling 25e2150 on pip-install-setup-docs into 079ea3d on master.

@richafrank richafrank force-pushed the pip-install-setup-docs branch from 128b678 to 8611a5e Compare November 29, 2017 20:57
@coveralls
Copy link

coveralls commented Nov 29, 2017

Coverage Status

Coverage remained the same at 87.372% when pulling 8611a5e on pip-install-setup-docs into 49a3a4a on master.

@coveralls
Copy link

coveralls commented Nov 29, 2017

Coverage Status

Coverage remained the same at 87.372% when pulling 8611a5e on pip-install-setup-docs into 49a3a4a on master.

@richafrank richafrank force-pushed the pip-install-setup-docs branch from 8611a5e to d0d96bb Compare November 30, 2017 15:17
@coveralls
Copy link

coveralls commented Nov 30, 2017

Coverage Status

Coverage remained the same at 85.92% when pulling bcddf4b on pip-install-setup-docs into f61d3df on master.

depends=['zipline/lib/adjustment.pxd'],
),
]
ext_modules = [
Copy link
Contributor

Choose a reason for hiding this comment

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

Wow, we have a lot of extensions. Probably not for this PR, but I wonder if we could consolidate these somehow. That might speed up some of our CI build times significantly I think.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yea, the pip install -e . of the builds takes 90+ seconds currently.

Copy link
Contributor

Choose a reason for hiding this comment

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

oof


.. code-block:: bash

$ pip install numpy Cython
Copy link
Contributor

Choose a reason for hiding this comment

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

This will give people the latest version of numpy. Do we support that?

Copy link
Member Author

Choose a reason for hiding this comment

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

AFAIK we do. If we don't, then we should update setup.py's REQ_UPPER_BOUNDS.

@freddiev4
Copy link
Contributor

Hi @richafrank anything I can do to help get this branch merged?

@richafrank richafrank force-pushed the pip-install-setup-docs branch 2 times, most recently from a1eff02 to 54e5c9e Compare July 3, 2018 14:29
@richafrank richafrank force-pushed the pip-install-setup-docs branch from 54e5c9e to bcddf4b Compare July 3, 2018 15:02
@richafrank
Copy link
Member Author

Hi @richafrank anything I can do to help get this branch merged?

I think we should get agreement with the team that the install workflow changes here are what we want, and that there aren't any broken scenarios.

@ssanderson
Copy link
Contributor

I'm 👍 on merging these changes as-is. The only thing we might want to add to this is an entry to the release notes telling people that they need to pre-install numpy now if they're using pip.

@ernestoeperez88 ernestoeperez88 removed their request for review January 16, 2020 19:08
@rapetter94
Copy link
Contributor

@ssanderson @richafrank should we merge once we add requirement to install numpy to release notes (per Scott's comment^)?

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.

5 participants