Willie Lopez added the comment:
Thank you anyway. I was able to finally resolve the issue, which did turn out
to be the environment variable PYTHONPATH. When compiling python from source,
that variable must be empty (not null). After emptying the string value the
compilation worked.
This probably has to do more with having two versions of python, the system and
our application side. The env variable is always set on our dev and app
servers. Not a good practice when compiling from source.
Thanks!
Willie Lopez
———-
willie.lo...@yahoo.com
970.481.8246
> On Apr 26, 2020, at 10:25 AM, Zachary Ware wrote:
>
>
> Zachary Ware added the comment:
>
> Hi Willie,
>
> Sorry this never got attention before 2.7 reached end-of-life, but as that
> has now happened, I'm closing the issue.
>
> That said, I suspect your issue here was with library search path; it wasn't
> actually 2.7.5 that was installed by the install of 2.7.16, but rather it was
> the system's 2.7.5 library that was loaded instead of the installation's
> 2.7.16 due to the latter's directory being either not on the search path or
> after the system's Python library location. I'm not sure if there's really a
> good way to have two separate patch versions of Python, both with shared
> libraries rather than static, without winding up with some confusion about
> which library should be loaded by which application.
>
> --
> nosy: +zach.ware
> resolution: -> out of date
> stage: -> resolved
> status: open -> closed
>
> ___
> Python tracker
> <https://bugs.python.org/issue37518>
> ___
--
___
Python tracker
<https://bugs.python.org/issue37518>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
