Displaying 3 results from an estimated 3 matches for "python2_sitearch".
2017 Mar 04
2
Python search path
...r
CentOS 7 (and eventually I want them to work in Fedora 25+ too)
These spec files must work with the user defines an alternate %{_prefix}
before building them.
This means that python components would be installed in /opt/libbitcoin
(or whatever) instead of in /usr so %{python2_sitelib} and
%{python2_sitearch} no longer would apply.
sys.path.append looks like the way to tell python about a new path to
look for stuff, but I'm guessing there are guidelines somewhere for how
that is suppose to properly done from within spec files.
Unfortunately I can't find them, and search engines are getting...
2017 Mar 04
1
Python search path
...25+ too)
>>
>> These spec files must work with the user defines an alternate %{_prefix}
>> before building them.
>>
>> This means that python components would be installed in /opt/libbitcoin
>> (or whatever) instead of in /usr so %{python2_sitelib} and
>> %{python2_sitearch} no longer would apply.
>>
>> sys.path.append looks like the way to tell python about a new path to look
>> for stuff, but I'm guessing there are guidelines somewhere for how that is
>> suppose to properly done from within spec files.
>>
>> Unfortunately I ca...
2017 Mar 04
0
Python search path
...want them to work in Fedora 25+ too)
>
> These spec files must work with the user defines an alternate %{_prefix}
> before building them.
>
> This means that python components would be installed in /opt/libbitcoin
> (or whatever) instead of in /usr so %{python2_sitelib} and
> %{python2_sitearch} no longer would apply.
>
> sys.path.append looks like the way to tell python about a new path to look
> for stuff, but I'm guessing there are guidelines somewhere for how that is
> suppose to properly done from within spec files.
>
> Unfortunately I can't find them, and s...