Antoine Pitrou <pit...@free.fr> added the comment: > So I'm gonna ask: when I modify *.c files, do I have to do something > else other than "./configure; make; make install" in order to see the > changes applied?
No. If you run the Python binary from the SVN checkout directory (rather than from an installation), _ssl should come from the build subdirectory, not from /usr/local/lib. Example here: $ pwd /home/antoine/cpython/newssl $ ./python -c "import _ssl; print _ssl.__file__" /home/antoine/cpython/newssl/build/lib.linux-x86_64-2.7/_ssl.so If _ssl is coming from "/usr/local/lib/...", it means that something modifies your sys.path so as to put that path before the path to the just built extension modules. I can't really investigate this point for you, but try using "python -E" instead. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8321> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
