Skip to content
This repository has been archived by the owner on Sep 4, 2023. It is now read-only.

Installation fails #28

Closed
janwirth opened this issue Dec 15, 2017 · 4 comments
Closed

Installation fails #28

janwirth opened this issue Dec 15, 2017 · 4 comments
Labels

Comments

@janwirth
Copy link

call(["pip", "install", "future"])

error: [Errno 2] No such file or directory: 'pip': 'pip'

OSX 10.12.6

Python installed through brew.

Pip updated to the latest version.

@jackfirth
Copy link
Owner

This probably has the same cause and solution as #8. Pyramda does bad things when installed to try and cleverly support python 2 and 3 with the same codebase. It should not do those things.

Alas, I don't have the bandwidth to actively maintain Pyramda and likely won't in the near future. If you're interested in contributing I would be quite happy to help point you in the right direction and answer any questions.

@janwirth
Copy link
Author

I probably don't have the bandwidth for long-term maintenance either but I would try to take this on.

So why is call(["pip", "install", "future"]) failing while it works in the shell and how would you go about fixing it?

@jackfirth
Copy link
Owner

I have no idea why it's failing and suspect it's not worth figuring out. I think the right approach is to just drop support for python 2 entirely since the maintenance period for it comes to an end in just over two years. That should let you rip out the fragile pasteurize code causing all these problems with minimal impact on the rest of Pyramda.

@jackfirth
Copy link
Owner

@FranzSkuffka This should hopefully be resolved by #36. I'm closing this issue for now, but if installation still fails for you please reopen it.

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

No branches or pull requests

2 participants