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

DM-25867: Make package pip installable #25

Merged
merged 11 commits into from Jul 13, 2020
Merged

DM-25867: Make package pip installable #25

merged 11 commits into from Jul 13, 2020

Conversation

timj
Copy link
Member

@timj timj commented Jul 8, 2020

No description provided.

@timj timj force-pushed the tickets/DM-25867 branch 3 times, most recently from 30d6426 to 914932d Compare July 9, 2020 00:59
@timj timj requested a review from TallJimbo July 9, 2020 02:17
python/lsst/__init__.py Show resolved Hide resolved
setup.cfg Outdated Show resolved Hide resolved
setup.py Show resolved Hide resolved
@@ -0,0 +1,6 @@
pybind11 >=2.5.0
Copy link
Member

Choose a reason for hiding this comment

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

So this directly blocks us from being able to use the pip/conda version to build the rest of the pipelines, right? It's a newer pybind11 than ndarray supports, and maybe some of our other code.

Copy link
Member Author

Choose a reason for hiding this comment

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

On the plus side this package must be compatible with the new pybind11. This was an arbitrary cut and paste from the pybind11 documentation. Since it worked with 2.5 and we know it builds with the stack version it's not a problem to change it.

@timj
Copy link
Member Author

timj commented Jul 9, 2020

Good news. With #26 implemented the build and test now only takes 3.5 minutes instead of 15 minutes. @smonkewitz thanks for having done all the work already!

timj added 6 commits July 9, 2020 14:31
The act of importing this seems to automatically enable
parallel builds.
There is no reason to fail catastrophically if yaml is missing
since the yaml feature we use is to ensure that when yaml is used
we serialize properly for yaml. In the absence of pyyaml we aren't
serializing to yaml.

We still retain it in the requirements.txt
This makes it easier to see what is going on in the output logs.
@timj timj merged commit d2e950e into master Jul 13, 2020
@timj timj deleted the tickets/DM-25867 branch July 13, 2020 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants