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

Some QuantStack libraries #35096

Closed
wants to merge 1 commit into from
Closed

Some QuantStack libraries #35096

wants to merge 1 commit into from

Conversation

mredaelli
Copy link
Contributor

Motivation for this change

Missing libraries from the QuantStack ecosystem

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.


let
pname = "gast";
version = "0.2.0";
Copy link
Member

Choose a reason for hiding this comment

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

these two should go into buildPythonPackage

pname = "gast";
version = "0.2.0";
in buildPythonPackage rec {
name = "${pname}-${version}";
Copy link
Member

Choose a reason for hiding this comment

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

and this removed

let version = "4.0.0"
; in
stdenv.mkDerivation {
version = version;
Copy link
Member

Choose a reason for hiding this comment

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

version is not an attribute of stdenv.mkDerivation

version = version;
name = "xsimd-${version}";

src = fetchurl {
Copy link
Member

Choose a reason for hiding this comment

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

maybe use fetchFromGitHub? At least insert ${version}

stdenv.mkDerivation rec {
version = "0.15.4";
name = "xtensor-${version}";

Copy link
Member

Choose a reason for hiding this comment

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

same

stdenv.mkDerivation rec {
version = "0.4.0";
name = "xtl-${version}";

Copy link
Member

Choose a reason for hiding this comment

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

same

name = "${pname}-${version}";

src = fetchurl {
url = "https://github.com/serge-sans-paille/gast/archive/master.zip";
Copy link
Member

Choose a reason for hiding this comment

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

fetching from master is a bad idea, not reproducible

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, but it doesn't have any release or tag. Should I go for a commit?

Copy link
Member

Choose a reason for hiding this comment

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

Yep. Do try to find the commit corresponding to the version.


let
pname = "pythran";
version = "0.8.4.post0";
Copy link
Member

Choose a reason for hiding this comment

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

into buildPythonPackage

pname = "pythran";
version = "0.8.4.post0";
in buildPythonPackage rec {
name = "${pname}-${version}";
Copy link
Member

Choose a reason for hiding this comment

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

and remove this

@@ -21869,6 +21874,8 @@ EOF
pysigset = callPackage ../development/python-modules/pysigset { };

us = callPackage ../development/python-modules/us { };


Copy link
Member

Choose a reason for hiding this comment

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

please don't include any whitespace changes

@FRidh
Copy link
Member

FRidh commented Feb 18, 2018

I have to think about what we should do with networkx considering we typically only permit a single version of a package.

@mredaelli
Copy link
Contributor Author

Thanks for detailed review. Much needed: it's my first try :)

@mredaelli
Copy link
Contributor Author

Should be ok now, except for networkx. Let me know if I should change something

@dotlambda
Copy link
Member

Networkx 2 is already in the staging branch. We should wait until that is merged.

@dotlambda
Copy link
Member

Networkx v2 is in master. Please rebase and remove your expression for v2.

@mmahut
Copy link
Member

mmahut commented Aug 3, 2019

What is the status of this pull request?

@FRidh
Copy link
Member

FRidh commented Aug 3, 2019

Nothing happening so closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants