This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients corona10, paul.moore, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2020-09-04.20:41:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1599252063.17.0.0828735854984.issue41627@roundup.psfhosted.org>
In-reply-to
Content
> If it is otherwise possible to user-only install both 32 and 64 bit versions, then using the same site-packages strikes me a bug

It's very easy to install both 32 and 64-bit runtimes (and it doesn't matter if they're user or system installs).

But when you're installing packages in the nt_user scheme (--user with pip), you can only use one or the other. If you install with 32-bit runtime first, then you'll get 32-bit binaries installed and the 64-bit runtime won't try and install the package again (or it'll delete it and replace it with one that only works with the 64-bit runtime).

With the change in PR 22098, the 32-bit interpreter will install to a different location.
History
Date User Action Args
2020-09-04 20:41:03steve.dowersetrecipients: + steve.dower, terry.reedy, paul.moore, tim.golden, zach.ware, corona10
2020-09-04 20:41:03steve.dowersetmessageid: <1599252063.17.0.0828735854984.issue41627@roundup.psfhosted.org>
2020-09-04 20:41:03steve.dowerlinkissue41627 messages
2020-09-04 20:41:03steve.dowercreate