[Python-Dev] Issue 10194 - Adding a gc.remap() function (original) (raw)
"Martin v. Löwis" martin at v.loewis.de
Tue Oct 26 19:56:36 CEST 2010
- Previous message: [Python-Dev] Issue 10194 - Adding a gc.remap() function
- Next message: [Python-Dev] Issue 10194 - Adding a gc.remap() function
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 26.10.2010 19:24, schrieb Peter Ingebretson:
--- On Tue, 10/26/10, Benjamin Peterson <benjamin at python.org> wrote:
Is there any reason that you'd want to do this?
http://doublestar.org/python-hot-loading-prototype/ I have a relatively large application written in Python, and a specific use case where it will significantly increase our speed of iteration to be able to change and test modules without needing to restart the application. We have experimented with different approaches to reloading and this one seems the most promising by a wide margin.
I think this then mandates a PEP; I'm -1 on the feature also.
In the PEP, you should explain what the alternatives are and why they don't work in the use cases of this feature. For example, I wonder why just changing the classes to have the updated methods isn't good enough. Or, if you want to be able to change the class of all instances of that class, why you can't track all instances explicitly.
In the PEP, you should then also explain what the limitations of the feature should. I.e. the feature should not be specified by its implementation, but have some abstract specification.
Regards, Martin
- Previous message: [Python-Dev] Issue 10194 - Adding a gc.remap() function
- Next message: [Python-Dev] Issue 10194 - Adding a gc.remap() function
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]