[issue1758146] Crash in PyObject_Malloc
Vaclav Slavik <[EMAIL PROTECTED]> added the comment: I'm able to reliably reproduce this bug (using Apache 2.2.8, otherwise same as above), although not with mod_python's simple tests, but only with Trac (apparently, Trac creates some threads while processing the request). How to reproduce: configure two Trac/mod_python locations in Apache config and set them to use different Python interpreters: SetHandler mod_python PythonHandler trac.web.modpython_frontend PythonOption TracEnv /srv/bakefile/trac PythonOption TracUriRoot / PythonInterpreter trac1 SetHandler mod_python PythonHandler trac.web.modpython_frontend PythonOption TracEnv /srv/bakefile/trac PythonOption TracUriRoot / PythonInterpreter trac2 (As far as this bug is concerted, this is the same as having two virtual hosts that both run Trac -- mod_python's default interpreter has the same name as the (virtual) host.) Then run Apache as "apache2 -X" to ensure that requests are handled by single handler serially and do $ curl http://your-server/trac1/wiki $ curl http://your-server/trac2/wiki The second command crashes Apache. If you change mod_python configuration to use the same interpreter names for both Trac instances, the crash doesn't happen (but of course, that prevents you from using different versions of Python modules in both vhosts). I'm attaching Valgrind log, but it's not very useful -- it's not deep enough and my server doesn't have enough memory for high enough value of --num-callers. -- nosy: +vslavik Added file: http://bugs.python.org/file10393/valgrind.log.gz _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1758146> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1758146] Crash in PyObject_Malloc
Vaclav Slavik <[EMAIL PROTECTED]> added the comment: > Does the PythonInterpreter option create multiple interpreters > within a single process Yes. > They aren't truly isolated interpreters and nobody I've asked has yet > provided a use case for it. If you ignore mod_python and mod_wsgi, then maybe, but mod_python is *the* use case for this. Running separate process for every web app and/or every virtual host on your server is expensive in terms of RAM usage (and this matters if you use virtual server - 256MB or less is not unusual). On the other hand, you need isolation for independent apps -- some modules may use globals, or you may want to be able to run both production and testing versions of the same app (i.e. different versions of the same Python module). ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1758146> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1758146] Crash in PyObject_Malloc
Vaclav Slavik <[EMAIL PROTECTED]> added the comment: > This could be done either by not using the normal import mechanism This is completely unrealistic suggestion, people use libraries and frameworks in their code, you're in effect suggestion that no library that could possibly be used in webapp should use (standard) import. I may be wrong, but I strongly suggest that you do talk to mod_python/wsgi people (who know much better than me) about what real-life uses of isolated interpreters are, before entertaining the idea of getting rid of the feature. ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1758146> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1758146] Crash in PyObject_Malloc
Vaclav Slavik <[EMAIL PROTECTED]> added the comment: I'm sorry, did you actually read my comments? Once again, this has nothing to do with threads and everything to do with isolation of independent Python apps running in the same *process*. Hope it got through this time :-/ ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1758146> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41744] NuGet python.props only works in python nuget, not other variants
New submission from Vaclav Slavik : NuGet automatically includes .props file from the build directory in the target using the package, but only if the file has the correct name: it must be $(id).props. This means that Python's support for this only works correctly in the python nuget packages, but not in pythonx86 and others, because the file is copied as python.props (instead of pythonx86.props etc) there too. -- components: Windows messages: 376577 nosy: paul.moore, steve.dower, tim.golden, vslavik, zach.ware priority: normal severity: normal status: open title: NuGet python.props only works in python nuget, not other variants type: behavior ___ Python tracker <https://bugs.python.org/issue41744> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41744] NuGet python.props only works in python nuget, not other variants
Change by Vaclav Slavik : -- keywords: +patch pull_requests: +21233 stage: -> patch review pull_request: https://github.com/python/cpython/pull/22154 ___ Python tracker <https://bugs.python.org/issue41744> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41744] NuGet python.props only works in python nuget, not other variants
Vaclav Slavik added the comment: Thank you, I didn't consider that situation. I forced-pushed an update to the PR now. I opted for duplicate file rather than including, because I think it imposes the least maintenance burden on keeping compatibility: the other alternative would mean - one more file - either a more complicated logic or the primary file including the compat one (so "normal" path slightly more convoluted) - tiny, but not 100% trivial difference between python nuget and the other ones. -- ___ Python tracker <https://bugs.python.org/issue41744> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41744] NuGet python.props only works in python nuget, not other variants
Vaclav Slavik added the comment: Sorry for the omission (fixed now), and thanks for your patience! -- ___ Python tracker <https://bugs.python.org/issue41744> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
