[Distutils] oneget python provider?

[Paul Moore]

On 14 January 2015 at 01:51, Vincent Povirk <madewokherd at gmail.com> wrote:
> On Tue, Jan 13, 2015 at 11:05 AM, Paul Moore <p.f.moore at gmail.com> wrote:
>> I'm sort of interested in this, but as far as I've been able to work
>> out, it's only available on Windows 8 and later. As I'm still on
>> Windows 7, that means I have limited opportunity to investigate.
>
> There's no installer for Windows 7 just yet (technically no installer
> for it at all, it's just been shipped in the installers of other
> things), but the .zip downloads linked from the github page
> (http://oneget.org/oneget.zip) should work.
>
> See https://github.com/OneGet/oneget/wiki/cmdlets for some hint on how
> to use it from its directory once extracted.

Cool, thanks. I'll take a look.

I guess the most obvious question about OneGet from a distutils-sig
(Python) perspective, is what is the expected process for a user who's
trying to do something with Python? At the moment, the process goes:

1. Go to www.python.org and locate the appropriate Python installer
for your system (2.7, 3.4, 32-bit vs 64-bit).
2. Run the installer, selecting "Add Python to PATH".
3. Go to a command prompt and type "pip install requests matplotlib whatever".
4. Start coding.

(Note for distutils-sig veterans, I know it's rarely *quite* this
easy, but this is the ideal, and it certainly can be as good as
this...)

What would be the equivalent experience with OneGet, and how would it
help with this? Given how easy the above is, it's hard to see the
benefits. If it's about fitting in with the wider ecosystem, I'd be
tempted to say we should wait till more people are using OneGet first.
Things are changing a lot in the Pythobn packaging world at the
moment, and adding more options at this stage is likely to be
counterproductive. (Note, I'm not saying I'm against OneGet - far from
it - just that I'm not sure we should be "early adopters" here...)

Paul