robhealey1 at gmail.com
Mon Apr 16 04:30:13 UTC 2012
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???
Rob G. Healey
> Could anyone explain why there are so many discrepancies between
> Python-2.7.2-12 and Python-3.3.02?
> 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.
Rob G. Healey
More information about the test