[Python-Dev] pyparallel and new memory API discussions...
Nick Coghlan
ncoghlan at gmail.com
Wed Jun 19 15:33:02 CEST 2013
More information about the Python-Dev mailing list
Wed Jun 19 15:33:02 CEST 2013
- Previous message: [Python-Dev] pyparallel and new memory API discussions...
- Next message: [Python-Dev] pyparallel and new memory API discussions...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 19 June 2013 23:10, Trent Nelson <trent at snakebite.org> wrote: > So, Victor, I'm interested to hear how the new API you're proposing > will affect this solution I've come up with for pyparallel; I'm > going to be absolutely dependent upon the ability to lock main > thread pages as read-only in one fell-swoop -- am I still going to > be able to do that with your new API in place? By default, nothing will change for the ordinary CPython runtime. It's only if an embedding application starts messing with the allocators that things might change, but at that point, pyparallel would break anyway. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] pyparallel and new memory API discussions...
- Next message: [Python-Dev] pyparallel and new memory API discussions...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list