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 skrah
Recipients brett.cannon, dino.viehland, eric.snow, methane, serhiy.storchaka, skrah
Date 2019-06-02.09:32:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559467928.57.0.116015194278.issue36839@roundup.psfhosted.org>
In-reply-to
Content
On Sun, Jun 02, 2019 at 02:38:21AM +0000, Inada Naoki wrote:
> What instance means?  code object? co_code?
> Anyway, Dino didn't propose such thing.  He only proposed accepting buffer object for code constructor.
> He didn't describe how to use buffer object.  Python doesn't provide share buffer object inter processes.

He did, at a high level. in the original mail:

"If code objects supported the buffer protocol it would be possible to load
 code from a memory mapped file which is shared across all of the processes."


It is not very detailed, but gives the rationale.  I assumed that the
new shared memory support would be used, but it would be nice to hear
more details.
History
Date User Action Args
2019-06-02 09:32:08skrahsetrecipients: + skrah, brett.cannon, dino.viehland, methane, eric.snow, serhiy.storchaka
2019-06-02 09:32:08skrahsetmessageid: <1559467928.57.0.116015194278.issue36839@roundup.psfhosted.org>
2019-06-02 09:32:08skrahlinkissue36839 messages
2019-06-02 09:32:08skrahcreate