New submission from Santiago Castro:
I see that you use some helpers to test command line utilities
(https://hg.python.org/cpython/file/default/Lib/test/test_cmd_line_script.py)
that would be useful to Python programmers. Please, consider to add them to the
standard library (or somewhere) to
New submission from Santiago Castro:
When installing Python (for example, version 3.5.2), if SQLite library and
headers are not installed in a default location (like $HOME/.local/include
instead of /usr/include), it should take it from there, and not fail to find
it. This behavior does work
Changes by Santiago Castro :
--
title: SQLite headers are not -> SQLite headers are not searched in custom
locations
___
Python tracker
<http://bugs.python.org/issu
Santiago Castro added the comment:
I tried with pyenv (https://github.com/yyuu/pyenv): pyenv install 3.5.2. Maybe
the error is from their side, but basically it downloads Python and compiles
it:
https://github.com/yyuu/pyenv/blob/master/plugins/python-build/install.sh#L24
Santiago Castro added the comment:
Okay, that did work. But shouldn't it call pkg-config, so I don't need to set
the flags manually?
I mean, I'm running this in my user's home, in a computer which I don't have
root access, and I used Linuxbrew (https://github.com
Santiago Castro added the comment:
Okay, I checked out again and bz2 and openssl were in standard paths in fact,
my bad. But I think python should also take into account pkg-config. I left a
Dockerfile with how I think it should work with pyenv and Linuxbrew:
https://github.com/bryant1410