This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients benjamin.peterson, flox, giampaolo.rodola, janssen, loewis, pitrou
Date 2010-04-05.22:21:43
SpamBayes Score 6.99441e-15
Marked as misclassified No
Message-id <1270506222.3446.23.camel@localhost>
In-reply-to <>
> 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?


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
$ ./python -c "import _ssl; print _ssl.__file__"

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.
Date User Action Args
2010-04-05 22:21:45pitrousetrecipients: + pitrou, loewis, janssen, giampaolo.rodola, benjamin.peterson, flox
2010-04-05 22:21:43pitroulinkissue8321 messages
2010-04-05 22:21:43pitroucreate