[Python-Dev] Impact of Windows PowerShell OneGet ?
v+python at g.nevcal.com
Thu Oct 30 18:48:28 CET 2014
On 10/30/2014 7:30 AM, "Martin v. Löwis" wrote:
>> Most likely, OneGet won't replace pip/PyPI, any more than apt or yum
>> does; but it may be worth having Python itself available that way.
>> That might simply mean having someone package up Python and put it on
>> an appropriate server, or maybe python.org could end up hosting a
> Python is already available in Chocolatey:
> Given that OneGet intends to support Chocolatey as a repository,
> it might just work already. All python.org would have to guarantee
> is stable URLs for the Python msi files.
It might. Thanks for that information.
Poking around the link, I discover a weirdness: the claim that the
package to install 32-bit Python on 64-bit systems is different than
installing the 32-bit Python on 32-bit systems. While the instructions
are explicit on what to do inside the chocolatey environment for all 3
cases (the third being 64-bit install on 64-bit systems), I'm baffled as
to why there is a difference, because there isn't when downloading
32-bit Python from python.org...
And there is a weird reference to chocolatey's -x86 parameter, and the
explanation seems to be that chocolatey has provision for installing
32-bit or 64-bit packages on 64-bit systems, but that the way Python is
included in chocolatey, that provision can't be used. Sounds very
strange, like whoever set this up either didn't understand Python, or
didn't understand chocolatey, or there is some limitation to the
chocolatey implementation of 32-bit vs 64-bit packages.
Maybe if I understand chocolatey, this wouldn't seem so weird.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev