[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: python2.2 -> python2.3



On Wed, 2004-10-13 at 12:51, Harald Hoyer wrote:
> Warren Togami wrote:
> > Alan Milligan wrote:
> >> What we have here doesn't really qualify as bugs.  Our stuff falls into
> >> two major components; (i) implementing the following macros:
> >>
> >> %pythonprefix /usr
> >> %__python %{pythonprefix}/bin/python
> >> %pythonversion %(python -c 'import sys;print(sys.version[0:3])')
> >> %pythonpath %{pythonprefix}/lib/python%{pythonversion}
> >> %pythoninclude %{pythonprefix}/include/python%{pythonversion}
> > 
> > 
> > Sorry, these changes are too invasive at this point, and even 
> > potentially wrong.  What about multilib?
> 
> %pythondir %(python -c 'from distutils import sysconfig; print sysconfig.get_python_lib(0,0,prefix=%{pythonprefix})')
> will return /usr/lib/.... on all archs for arch independent stuff
> 
> %pyexecdir %(python -c 'from distutils import sysconfig; print sysconfig.get_python_lib(1,0,prefix=%{pythonprefix})')
> will return /usr/lib{,64}/... for arch dependent stuff

Aren't get_python_lib(0) and get_python_lib(1) enough?  See also #125472

BTW, Python makes a distinction between arch independent and arch
dependent include dirs as well, so something like the above should be
used to get them too, with get_python_inc().


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]