Message184357
| Author |
epu |
| Recipients |
Eli_B, Roy.Jacobson, Stephen.White, brian.curtin, carwyn, cgohlke, dontbugme, epu, eric.araujo, erluk, ghazel, jaraco, jerome.radix, jkloth, loewis, menekali@gmail.com, pje, r.david.murray, santoso.wijaya, srid, ssbarnea, tarek, vr.gamer |
| Date |
2013年03月16日.22:06:18 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1363471578.64.0.890532270036.issue6792@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I would like to investigate this issue, but I need more information regarding the bug and the expected behavior. Is this specifically that an x64 windows python that generates a bdist (msi output) runs and can't find the x64 interpreter because of syswow registry redirection? That is, packaging should be able to find the interpreter bitness that generated the msi in the first place (and no-other bitness)?
There are python sprints this week at PyCon, but I cannot attend them. Clarifying the expected behavior this week will help me write tests and investigate/fix (if it is in my ability). |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年03月16日 22:06:18 | epu | set | recipients:
+ epu, loewis, pje, jaraco, ghazel, tarek, jkloth, eric.araujo, dontbugme, r.david.murray, carwyn, ssbarnea, brian.curtin, srid, cgohlke, erluk, Stephen.White, santoso.wijaya, menekali@gmail.com, jerome.radix, Eli_B, vr.gamer, Roy.Jacobson |
| 2013年03月16日 22:06:18 | epu | set | messageid: <1363471578.64.0.890532270036.issue6792@psf.upfronthosting.co.za> |
| 2013年03月16日 22:06:18 | epu | link | issue6792 messages |
| 2013年03月16日 22:06:18 | epu | create |
|