RetroSearch Browse

Mon Mar 10 16:35:46 CET 2014 · https://mail.python.org/pipermail/python-dev/2014-March/133025.html

   Hi Paul.

On 10.3.2014. 14:54, Paul Moore wrote:
> On 10 March 2014 13:03, Jurko Gospodnetić <jurko.gospodnetic at pke.hr> wrote:
>> Is this as issue or desired behaviour? Should I open an issue for it?
>
> Sounds like a bug, but a pretty long-standing one. I can't think that
> the registry schema Python uses would *ever* have distinguished (the
> WOW64 component of the all-users entries is a system-generated thing,
> AIUI).
>
> So yes, raise a bug, but (a) it would be useful to test whether the
> same bug exists in 3.3 and 2.7, and (b) it's going to be tricky to fix
> without a backward-incompatible change to the registry settings (which
> will affect things like the launcher and virtualenv, for a start).

   Reported as issue #20883 (http://bugs.python.org/issue20883). I'll 
report the extra details there then.

   Best regards,
     Jurko Gospodnetić

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-March/133025.html below:

[Python-Dev] Windows 'for current user' installation