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

mac builds for multithreading #18

Closed
fscottfoti opened this issue Aug 28, 2014 · 5 comments
Closed

mac builds for multithreading #18

fscottfoti opened this issue Aug 28, 2014 · 5 comments

Comments

@fscottfoti
Copy link
Contributor

I want to open an issue that keeps the latest on multithreaded mac builds. Looks like you can now run "pip install pandana" on mac but you get the single threaded version by default because the default C++ compiler on Mac doesn't support openmp.

Multithreading on Mac is possible - I use it all the time - but requires getting a version of GCC. @jiffyclub - do you think we should list the steps here or on the wiki or in the sphinx docs or ...?

@jiffyclub
Copy link
Member

We should have a section in the Sphinx docs on installation and put in a section about building on Mac with OpenMP.

@fscottfoti
Copy link
Contributor Author

@jiffyclub I'm going to hijack this thread and make a v1.0 release to-do list.

  • Add installation section to sphinx docs (specifically for openmp on mac)
  • Figure out what to do about utils.py, which is dependent on the osm branch of geopandas - probably should move back in to the notebook as an "experimental notebook"
  • Fix the rst issue on pypi?

Gonzalo is going to look at getting a version of contraction hierarchies that is BSD but I think we should release the AGPL version for v1.0 and just not take contributions. Then hopefully we can get a BSD version of some kind soon and take contributions.

@jiffyclub
Copy link
Member

We've already done a v0.1 release, and your checklist doesn't have anything that necessarily requires a new release.

  • We can update the published docs at any time independent of releases.
  • utils.py is included in the release, but because we don't specify an explicit dependence on any geopandas stuff it doesn't break anything. People could try to use it, though, and your example notebook could explain how. (Unless the utils.py that's in the release is incomplete or broken.)
  • We can fix the rst issue on PyPI manually without doing a release. I expect we're hitting this issue: http://stackoverflow.com/questions/16367770/my-rst-readme-is-not-formatted-on-pypi-python-org. It'll require some manual editing to fix.
    • (Related question: do we want to convert the README from Markdown to RST for compatibility with PyPI?)

@fscottfoti
Copy link
Contributor Author

This sounds good. I suppose I really want to get a blog post on Pandana as soon as we're ready. It sounds like we're close - basically a couple of extra notes in the install docs and on the anything score notebook. BTW - I just cloned pandana and it was still 32MB - is this the expected size at this point?

@fscottfoti
Copy link
Contributor Author

btw - I'm ok with converting the readme to rst.

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