Andrea Griffini agriff at tin.it
Mon Mar 23 18:59:10 CET 2015

• Previous message (by thread): [Python-Dev] Installing Python to non-ASCII paths
• Next message (by thread): [Python-Dev] --with-valgrind and --enable-shared
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Hello,

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.

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?

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

Andrea Griffini
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150323/b62342f1/attachment.html>

---

• Previous message (by thread): [Python-Dev] Installing Python to non-ASCII paths
• Next message (by thread): [Python-Dev] --with-valgrind and --enable-shared
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list