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 | belopolsky |
|---|---|
| Recipients | belopolsky, georg.brandl, glyph, nnorwitz, schmir |
| Date | 2008年03月27日.14:05:17 |
| SpamBayes Score | 0.17669795 |
| Marked as misclassified | No |
| Message-id | <1206626719.9.0.931395217388.issue2375@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I have never had a problem of different python versions coexisting on the same machine, but having 32-bit and 64-bit python coexist is much harder. Particularly when 32-bit python is compiled on the 64-bit OS (using -m32 flag). There is a related issue1294959 highlighting this problem. See also issue1536339, issue1553166, and issue858809. Ideally, I would like to see a mechanism that would allow both standard library and user modules to share machine independent (*.py{,c,o}) files while having separate locations for 32-bit and 64-bit C modules. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月27日 14:05:20 | belopolsky | set | spambayes_score: 0.176698 -> 0.17669795 recipients: + belopolsky, nnorwitz, georg.brandl, schmir, glyph |
| 2008年03月27日 14:05:19 | belopolsky | set | spambayes_score: 0.176698 -> 0.176698 messageid: <1206626719.9.0.931395217388.issue2375@psf.upfronthosting.co.za> |
| 2008年03月27日 14:05:18 | belopolsky | link | issue2375 messages |
| 2008年03月27日 14:05:17 | belopolsky | create | |