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.

Sign up for GitHub

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

Jump to bottom

Consider porting python 3.4 forkserver into billiard #127

Closed
jamescasbon opened this issue Nov 12, 2014 · 2 comments
Closed

Consider porting python 3.4 forkserver into billiard #127

jamescasbon opened this issue Nov 12, 2014 · 2 comments

Comments

@jamescasbon
Copy link

There are quite a few people, including Ipython notebook users who could benefit from this feature. Is billiard the right place for this?

I note that subprocess32 already has the c extension backported that does the forking.
@jamescasbon jamescasbon changed the title Consider porting python 3.4s forkserver into billiard Consider porting python 3.4 forkserver into billiard Nov 12, 2014
@ask
Copy link
Contributor

ask commented Nov 12, 2014

We have only implemented execv so far, not forkserver.

The idea is that the billiard version number will begin with the Python version it's based from, so billiard 3.3.0.18 is cpython 3.3.0, billiard bugfix release 18. A lot has changed in Python 3.4, a lot of the code is refactored so it may require more effort to port over.

@ask
Copy link
Contributor

ask commented Apr 17, 2015

Forkserver is in master now, but I haven't actually tried it

@ask ask closed this as completed Apr 17, 2015
@davemt davemt mentioned this issue Oct 28, 2015
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ask @jamescasbon