On Mon, Mar 23, 2015 at 1:59 PM Andrea Griffini <agriff@tin.it> wrote:

does it have any sense for a linux distribution (arch to be specific) to provide default Python package compiled with valgrind support? I thought this flag was just about silencing false positives generated by valgrind (in other words a workaround for "bugs" of another software) and useful only when developing Python itself or C extensions.

It's not really our place to say if it makes sense for Arch to compile with valgrind flags turned on. It really depends on how they use Python in their Linux distribution and what their own goals are.

The same distribution also compiles by default to a shared library and this has a quite noticeable impact on performance on x64 (surprisingly for me) for CPU bound processing; in a few test cases I measured valgrind+shared Python running at 66% the speed of plain ./configure && make Python on my system. Is this setting reasonable for general users?

Once again, it all depends on how Arch uses Python.

If they are good defaults, why aren't them the default?

That's a question for Arch Linux and not us.