You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be good to expand on that and have a whole page with more information:
Explain the GIL (as of Python 3.13, it can be disabled, but this is not yet ready for general usage: requires a separate Python build, lack of compatibility with modules using the C-API, 5–10% slowdown for single-threaded code)
Difference between ThreadPoolExecutor and ProcessPoolExecutor
I’m not sure about how to handle async/await. Since it’s conceptually more challenging, maybe it’s better to keep that section very short and high level? And just say “if you have a use case for this [enumerate what those would be], then see the following links for further information”?
The text was updated successfully, but these errors were encountered:
Yes, whilst the new example from #59 is clearly worth showing it feels like it's missing some context that more novice course attendees would benefit from.
Similar applies to your astrophysics code here, it would be some of the harder to parse(?) code from the course so some handholding would be preferable (and maybe more detail in an instructor note?).
I’m not sure about how to handle async/await. Since it’s conceptually more challenging, maybe it’s better to keep that section very short and high level?
Yeah something to the effect of, "more advanced parallel concepts such as x,y exist in Python however these are outside the scope of the course (would require a course of their own!)...learn more here".
In #59 I’ve added a code sample using a
concurrent.futures.ThreadPoolExecutor
to parallelise downloading files.I think it would be good to expand on that and have a whole page with more information:
ThreadPoolExecutor
andProcessPoolExecutor
I’ve got an example for
ThreadPoolExecutor
already (in #59); forProcessPoolExecutor
I could adapt an example from an astrophysics code I’ve developed.I’m not sure about how to handle async/await. Since it’s conceptually more challenging, maybe it’s better to keep that section very short and high level? And just say “if you have a use case for this [enumerate what those would be], then see the following links for further information”?
The text was updated successfully, but these errors were encountered: