-
Notifications
You must be signed in to change notification settings - Fork 7
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
Clarify requirements for local setup in README #60
Comments
Oh boy, it's been a while. I'll take a look. |
@eebbesen I'm running on Ubuntu 18 and don't appear to be getting any |
Welp, that was an interesting little ponder through past build process decisions. I added a bit of clarifying text to the README to describe how the current dev flow is expected to go (although that process could probably use a good shaking out), feel free to add any further questions to the PR #61 . Given that it addresses those concerns I can merge it in. I don't think that python3.5 or python3.6 should matter. I'll need to take a look at bumping that in pipenv. Can't remember how much of a pain that makes itself. |
@kjschiroo here's what I get when following those instructions for dev setup. I'm on OS X using pyenv to manage my Python versions. (And yes, "numpy" :).) Here's a gist with the full error: https://gist.github.com/eebbesen/de1dabbc0ae8337dc8cf3bea31d8cf44 |
Hm... that's odd. It looks like you are trying to build |
I can try working on it in an Ubuntu VM, though, I'd rather not distract from getting this setup on OS X until we have folks who don't have access to other methods.
|
pipenv install --dev
on OS X@kjschiroo can you clarify?
The text was updated successfully, but these errors were encountered: