Re: Python discrepancies...
On Sun, 2012-04-15 at 00:18 -0700, Rob Healey wrote: > Greetings: > > Could anyone explain why there are so many discrepancies between > Python-2.7.2-12 and Python-3.3.02? > > This is from Python-3.3.0a2: > -- > [Frog@DancingSquirrels Documents]$ python3 > Python 3.3.0a2 (default, Apr 13 2012, 16:55:12) This appears to be a python that you've built locally from the 3.3.0a2 tarball; the giveaway are all the "local"s in the sysconfig e.g. this one: [...snip...] > platstdlib = /usr/local/lib/python3.3 [...snip...] > From Python-2.7.2-12 This is the python from rpm [...] > stdlib = /usr/lib64/python2.7 The "lib64" stuff is from a patch we apply "downstream" when we build our RPMs in order to allow both 32-bit and 64-bit build of python to be installed: 32-bit builds go in /usr/lib; 64-bit ones go in /usr/lib64. The jargon name for this is "multilib". Hope this is helpful Dave -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: python discrepancies
On Mon, Apr 16, 2012 at 6:30 AM, Rob Healey wrote: > Greetings: > > The only part that I had in question was why were there in Python2.7, > the use of /usr/lib64... > > In Python3.3, it always used /usr/lib ... > > Why would Python3.3 which I did compile from source not see that I > have a 64bit computer and use it instead for the directories??? Because multilib is not used by upstream directly and therefore needs be patched in in any build: http://pkgs.fedoraproject.org/gitweb/?p=python3.git;a=blob;f=python-3.2.3-lib64.patch Greetings, Tom -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
re: python discrepancies
Greetings: The only part that I had in question was why were there in Python2.7, the use of /usr/lib64... In Python3.3, it always used /usr/lib ... Why would Python3.3 which I did compile from source not see that I have a 64bit computer and use it instead for the directories??? Sincerely yours, Rob G. Healey > > Could anyone explain why there are so many discrepancies between > Python-2.7.2-12 and Python-3.3.02? [snip] > Of course, I do not know if this is a bug or not, but I though that I > would present it here first? What about this do you consider a bug? If you built the package that is failing, wouldn't that imply that *you* did something incorrectly? > I am not talking about about how much more there are in > Python-3.3.0a2... I am talking about the architecture??? In 2.7.3, > which was packaged by Fedora, has the correct architecture of x86_64. > Python-3.3.0a2, which was compiled by me, has the architecture as > 32bit ... I'm not sure I understand your question, but I'll try to answer what I think it is. The Fedora package for python 2.7 x86_64 installs itself to the proper locations for x86_64. The Fedora package for python 3.2 installs itself to the proper locations for x86_64. Both in F17. The package you built, is partially installing to /usr/local. This is the default for most raw source on the web. *You* have to change the configuration, usually with a setting in configure, if you want it to install elsewhere. The Fedora packagers usually do this. Perhaps you could download the source RPM for the python 3.2 package from Fedora F17, and tweak it to compile your payload (the tarball for python 3.3)? If I've missed your point completely, apologies. -- Sincerely yours, Rob G. Healey -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Python discrepancies...
On Sun, 15 Apr 2012 00:18:17 -0700 Rob Healey wrote: > Greetings: > > Could anyone explain why there are so many discrepancies between > Python-2.7.2-12 and Python-3.3.02? [snip] > Of course, I do not know if this is a bug or not, but I though that I > would present it here first? What about this do you consider a bug? If you built the package that is failing, wouldn't that imply that *you* did something incorrectly? > I am not talking about about how much more there are in > Python-3.3.0a2... I am talking about the architecture??? In 2.7.3, > which was packaged by Fedora, has the correct architecture of x86_64. > Python-3.3.0a2, which was compiled by me, has the architecture as > 32bit ... I'm not sure I understand your question, but I'll try to answer what I think it is. The Fedora package for python 2.7 x86_64 installs itself to the proper locations for x86_64. The Fedora package for python 3.2 installs itself to the proper locations for x86_64. Both in F17. The package you built, is partially installing to /usr/local. This is the default for most raw source on the web. *You* have to change the configuration, usually with a setting in configure, if you want it to install elsewhere. The Fedora packagers usually do this. Perhaps you could download the source RPM for the python 3.2 package from Fedora F17, and tweak it to compile your payload (the tarball for python 3.3)? If I've missed your point completely, apologies. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Python discrepancies...
Greetings:
Could anyone explain why there are so many discrepancies between
Python-2.7.2-12 and Python-3.3.02?
This is from Python-3.3.0a2:
--
[Frog@DancingSquirrels Documents]$ python3
Python 3.3.0a2 (default, Apr 13 2012, 16:55:12)
[GCC 4.7.0 20120322 (Red Hat 4.7.0-1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> for pathname in sysconfig.get_path_names():
... print('%s = %s' % (pathname, sysconfig.get_path(pathname)))
...
confdir = /etc
doc = /usr/share/doc/{distribution.name}
libdir = /usr/lib
info = /usr/share/info
icon = /usr/share/pixmaps
platstdlib = /usr/local/lib/python3.3
include = /usr/local/include/python3.3m
config = /etc/{distribution.name}
purelib = /usr/local/lib/python3.3/site-packages
datadir = /usr/share
appdata.disposable = /var/cache/{distribution.name}
platinclude = /usr/local/include/python3.3m
appdata.persistent = /var/lib/{distribution.name}
appdata.arch = /usr/lib/{distribution.name}
platlib = /usr/local/lib/python3.3/site-packages
statedir = /var
help = /usr/share/{distribution.name}
appdata = /usr/share/{distribution.name}
data = /usr/local
man = /usr/share/man
local = /home/Frog/.local/{distribution.name}
stdlib = /usr/local/lib/python3.3
scripts = /usr/local/bin
From Python-2.7.2-12
--
[Frog@DancingSquirrels Documents]$ python
Python 2.7.3 (default, Apr 13 2012, 14:45:43)
[GCC 4.7.0 20120322 (Red Hat 4.7.0-1)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> for pathname in sysconfig.get_path_names():
... print('%s = %s' % (pathname, sysconfig.get_path(pathname)))
...
stdlib = /usr/lib64/python2.7
platstdlib = /usr/lib64/python2.7
purelib = /usr/lib/python2.7/site-packages
platlib = /usr/lib64/python2.7/site-packages
include = /usr/include/python2.7
scripts = /usr/bin
data = /usr
Of course, I do not know if this is a bug or not, but I though that I
would present it here first?
I am not talking about about how much more there are in
Python-3.3.0a2... I am talking about the architecture??? In 2.7.3,
which was packaged by Fedora, has the correct architecture of x86_64.
Python-3.3.0a2, which was compiled by me, has the architecture as
32bit ...
--
Sincerely yours,
Rob G. Healey
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
