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

multiprocessing & greenlet concurrency #484

Closed
nedbat opened this issue Apr 8, 2016 · 2 comments
Closed

multiprocessing & greenlet concurrency #484

nedbat opened this issue Apr 8, 2016 · 2 comments
Labels
enhancement New feature or request

Comments

@nedbat
Copy link
Owner

nedbat commented Apr 8, 2016

Originally reported by Luca Sbardella (Bitbucket: lsbardel, GitHub: lsbardel)

I need to test coverage on an library which uses both greenlets and multiprocessing.
However the concurrency flag allows one only.
How about to allow for concurrency=multiprocessing,greenlet for example?

Until now I have used the coverage API to test for coverage in pulsar but I would like to move away form that and use coverage command line and configuration files only.
@nedbat
Copy link
Owner Author

nedbat commented Jul 4, 2016

The concurrency option in the configuration file can now be multi-valued, as of 31958372c1ca (bb).

This won't work from the command line, since the command-line options are not passed to the multi-processing sub-processes.

@nedbat
Copy link
Owner Author

nedbat commented Jul 5, 2016

Original comment by Luca Sbardella (Bitbucket: lsbardel, GitHub: lsbardel)

👍 thanks for this, very much appreciated!

@nedbat nedbat closed this as completed Jul 5, 2016
@nedbat nedbat added minor enhancement New feature or request labels Jun 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nedbat