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
pythonPackages.pymc3 init at 3.2 #39660
Conversation
sha256 = "0fw888zd2s7f5zxm9f98ss93qhwv0sqnbdy21ipj33ccqgakhpz0"; | ||
}; | ||
|
||
doCheck = true; |
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.
no need for this, it is set automatically
install_reqs.append('enum34') | ||
|
||
-test_reqs = ['pytest', 'pytest-cov'] | ||
+test_reqs = ['pytest'] # no need for test coverage info in Nix builds |
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.
I'd prefer using substituteInPlace
in postPatch
, because a patch generally requires more maintenance work.
@GrahamcOfBorg build python2.pkgs.patsy python3.pkgs.patsy |
Success on x86_64-linux (full log) Attempted: python2.pkgs.patsy, python3.pkgs.patsy Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: python2.pkgs.patsy, python3.pkgs.patsy Partial log (click to expand)
|
@GrahamcOfBorg build python2.pkgs.pymc3 python3.pkgs.pymc3 |
Failure on x86_64-linux (full log) Attempted: python2.pkgs.pymc3, python3.pkgs.pymc3 Partial log (click to expand)
|
postPatch = '' | ||
substituteInPlace setup.py --replace \ | ||
"test_reqs = ['pytest', 'pytest-cov']" \ | ||
"test_reqs = ['pytest']" |
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.
It will require even less maintenance if using
substituteInPlace setup.py --replace ", 'pytest-cov'" ""
pkgs/top-level/python-packages.nix
Outdated
@@ -10135,7 +10135,9 @@ in { | |||
|
|||
pygraphviz = callPackage ../development/python-modules/pygraphviz { }; | |||
|
|||
pymc3 = callPackage ../development/python-modules/pymc3 { }; | |||
pymc3 = if pythonAtLeast "3.5" |
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.
Please use disabled = pythonOlder "3.5"
instead.
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.
You should
- base your PR on master instead
- turn your 6 commits into 2 (one for each package)
Failure on aarch64-linux (full log) Attempted: python2.pkgs.pymc3, python3.pkgs.pymc3 Partial log (click to expand)
|
The manual here should be updated as it explicitly asks not to work with the master branch (contradicting what is written in the repo's README). Speaking of commits granularity, isn't it easy for a reviewer to squash when accepting? I thought it is easier to see how the review comments are acted upon when one add commits on top instead of force pushing. I guess I should make another PR based on master then. |
The last bullet point in the manual section you linked to clearly states
|
Indeed, TLDR on my side. Rebased and collapsed PR is at #39662 |
This is an updated version of #32416 rebased onto release-18.03 branch.
Motivation for this change
Adds the latest stable version of
pymc3
to Python packages and updatepatsy
(required by it) from 0.3.0 to 0.5.0.pymc3
of the major Bayesian inference libraries (along withstan
,BUGS
,JAGS
and, to a lesser extent,edward
).Things done