This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients Martin Ritter, davin, devin, docs@python, r.david.murray, rhettinger, sbt
Date 2016-07-04.16:55:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1467651321.06.0.717868727807.issue27422@psf.upfronthosting.co.za>
In-reply-to
Content
To clarify the GIL issue (for davin, I guess? :): if the library you are using to interface with the FORTRAN code drops the GIL before calling the FORTRAN, then you *can* take advantage of multiple cores.  It is only the python code (and some of the code interacting with the python objects) that is limited to executing on one core at a time.  (As far as I know it isn't restricted to be the *same* core unless you set CPU affinity somehow, and I have no idea if it improves performance to use CPU affinity or not).
History
Date User Action Args
2016-07-04 16:55:21r.david.murraysetrecipients: + r.david.murray, rhettinger, docs@python, devin, sbt, davin, Martin Ritter
2016-07-04 16:55:21r.david.murraysetmessageid: <1467651321.06.0.717868727807.issue27422@psf.upfronthosting.co.za>
2016-07-04 16:55:21r.david.murraylinkissue27422 messages
2016-07-04 16:55:20r.david.murraycreate