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

determine libpython at Pkg.build time, not at runtime #169

Merged
merged 1 commit into from
Jul 23, 2015

Conversation

stevengj
Copy link
Member

See discussion in #167.

With Base.compile(:PyCall), the load time is currently down to about 2 seconds on my machine. I'm not sure how to get it down further, although it should be possible.

cc: @malmaud, @jakebolewski

@malmaud
Copy link
Contributor

malmaud commented Jul 21, 2015

I tested locally and it decreases load time from ~4s to ~2s.

@stevengj
Copy link
Member Author

I just pushed a few precompilations that get it down to 1.3 seconds on my machine. (I'm guessing the improvements on Windows, compared to the old PyCall, may be even greater.)

stevengj added a commit that referenced this pull request Jul 23, 2015
determine libpython at Pkg.build time, not at runtime
@stevengj stevengj merged commit 84eb29a into master Jul 23, 2015
@stevengj stevengj deleted the staticcompile branch July 23, 2015 15:57
@stevengj
Copy link
Member Author

Oh crap, I checked in deps.jl, not build.jl. No, it's there, I was looking at the wrong version. Whew.

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

Successfully merging this pull request may close these issues.

2 participants