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

pkg: pycrypto #49

Closed
InLaw opened this issue Aug 19, 2020 · 5 comments
Closed

pkg: pycrypto #49

InLaw opened this issue Aug 19, 2020 · 5 comments

Comments

@InLaw
Copy link

InLaw commented Aug 19, 2020

error:

attribute 'src' in selection path 'python3Packages."pycrypto".src' not found


it has no src because it is not itself
https://github.com/InLaw/nixpkgs/blob/master/pkgs/development/python-modules/pycrypto/default.nix

@cript0nauta
Copy link
Owner

Wow, I wasn't expecting the nixpkgs source to have so many hacks for Python packages. This certainly makes things harder for pynixify.

I think I'll add a command line option that ignores parsing the requirements of the specified packages. This will fix this issue and maybe others related to nixpkgs hacks.

@InLaw
Copy link
Author

InLaw commented Aug 19, 2020

would be nice to specify

  • a pkg name and that for this to ignore e.g. the requirements
    (that it is not done globally only because one package needs it)

@cript0nauta
Copy link
Owner

Fixed in 6ba2231. I preferred to add some extra code to handle the pycrypto case rather than adding an additional command line option. I want pycrypto to be usable out of the box, not requiring some complicated option in order to make it work.

Thanks for reporting!

@InLaw
Copy link
Author

InLaw commented Aug 23, 2020

My thought was not a cmd option but

  • via the .nix config
    (but the pkgs is not top prio for me ..)

@cript0nauta
Copy link
Owner

If you want to override the requirements of an existing Nix package, you can add a local nixpkgs overlay as described here: #35 (comment). Instead of the doCheck = false;, you could put something like buildInputs = [ python-self.some_dependency ];.

Keep in mind that doing this affects reproducibility between machines, since pynixify could fail when it's run in machines without the custom overlays. #15 would solve this problem, but currently it's a low priority issue.

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

No branches or pull requests

2 participants