Python lib64 patch

The problem with 64 bit builds should be discussed before we release 2. Can someone update the priority so that this is looked at before the 2.

I think this is duplicate of issue If I understand correctly, using lib32 or lib64 is a kludge. Please note another aspect of this problem will bite all Python developers on Ubuntu Here's a fix that works for me on Ubuntu I should note that I'd love to backport this to Python 3. A proper fix is to introduce sys.

I retract my patch for this bug because the issue described here is actually different than the one I want to fix. On I currently think that sys. I disagree about sys. Examples architecture: libdir in Gentoo: x libx32 mips o lib mips n lib32 mips n lib Is there agreement on what needs doing here?

Also see The downstream patch we currently use in Fedora [0]. Attached is a patch that I'd like to propose for inclusion. I don't think we need a PEP for this, however I would like to name the new macro libsubdir, or sublibdir, to make it clear it's just the libdir component.

Pinging here. I closed bpo as a duplicate of this issue. See also bpo "Default Python 3. See also bpo : "setup. I marked bpo "Python 2. New changeset cae53fafdec1aafcbdeedf by Miss Islington bot in branch '3.

New changeset ac6f4d2dbc0ff88ebcb7b7fe55cf2ac by Miss Islington bot in branch '3. For reference: issue Ooops, SuSE has 2 patches. Why "sys. See also bpo : "freeze. New changeset fd9bc3a2fd6ebc5fe42 by Victor Stinner in branch 'master': bpo : Add sys.

I chose to exclude setup. Another related issue is bpo : "Default Python 3. I close this very old issue 15 years old! If you don't use the new --with-platlibdir configuration option, Python 3. Can you propose a PR with your doc enhancement? Ok, it seems that I misunderstood it at first. New changeset aadb2cdaa25dfcff by Miss Islington bot in branch '3. See issue - Build failed. Build succeeded. Zuul success. Jobs result is success 2 years ago. Zuul pending. Jobs result is pending 2 years ago.

Zuul failure. How the system decides which directory to go when python is requested, and how it finds the packaged i installed? As to how it finds the packages is contained in sys. The more detailed answer on how packages get there requires a bit of understanding about how python works in terms of it's own layout.

What we're interested in is part of the standard library called distutils. This is the workhorse, note there are also tools built on top of this setuptools and a fork called distribute at the moment trying to improve python packaging. This patch is conditionally applied in the RPM spec for python on architectures where the lib dir is lib We now have a condition on distutils that now changes what distutils. You can experiment with calling this with various options in a python interpreter:.

So when using building a python package using distutils or the layers built on top of it we will at some point ask the system configuration where the right place to put the files are, depending on if it is a system or platform lib it'll go in lib64 else it'll go in lib.

If you look at the Fedora Python Packaging documentation or use the fedora rpmdev tool to create a skeletal python spec rpmdev-newspec python-foo you'll see detailed comments of how fedora sets variables for the rpm build based on calling this function. Sign up to join this community. The best answers are voted up and rise to the top. Milestone Copy link. Member Author.

Not sure. Add clause to silence warning for Slackware bug Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.