Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #96072 > unrolled thread

Wheels For ...

Back to article view | Back to comp.lang.python

Contents

  Wheels For ... "Sven R. Kunze" <srkunze@mail.de> - 2015-09-06 19:33 +0200
    Re: Wheels For ... Ned Batchelder <ned@nedbatchelder.com> - 2015-09-06 13:06 -0700
      Re: Wheels For ... "Sven R. Kunze" <srkunze@mail.de> - 2015-09-07 18:52 +0200

#96072 — Wheels For ...

Hi folks,

currently, I came across http://pythonwheels.com/ during researching how 
to make a proper Python distribution for PyPI. I thought it would be 
great idea to tell other maintainers to upload their content as wheels 
so I approached a couple of them. Some of them already provided wheels.

Happy being able to have built my own distribution, I discussed the 
issue at hand with some people and I would like to share my findings and 
propose some ideas:

1) documentation is weirdly split up/distributed and references old material
2) once up and running (setup.cfg, setup.py etc. etc.) it works but 
everybody needs to do it on their own
3) more than one way to do (upload, wheel, source/binary etc.) it (sigh)
4) making contact to propose wheels on github or per email is easy 
otherwise almost impossible or very tedious
5) reactions went evenly split from "none", "yes", "when ready" to "nope"

None: well, okay
yes: that's good
when ready: well, okay
nope: what a pity for wheels; example: 
https://github.com/simplejson/simplejson/issues/122

I personally find the situation not satisfying. Someone proposes the 
following solution in form of a question:

Why do developers need to build their distribution themselves?

I had not real answer to him, but pondering a while over it, I found it 
really insightful. Viewing this from a different angle, packaging your 
own distribution is actually a waste of time. It is a tedious, 
error-prone task involving no creativity whatsoever. Developers on the 
other hand are actually people with very little time and a lot of 
creativity at hand which should spend better. The logical conclusion 
would be that PyPI should build wheels for the developers for every 
python/platform combination necessary.


With this post, I would like raise awareness of the people in charge of 
the Python infrastructure.


Best,
Sven

[toc] | [next] | [standalone]

#96081

On Sunday, September 6, 2015 at 1:33:58 PM UTC-4, Sven R. Kunze wrote:
> 
> Why do developers need to build their distribution themselves?
> 
> ...
> 
> With this post, I would like raise awareness of the people in charge of 
> the Python infrastructure.

Sven, you ask a question, and then say you are trying to raise awareness.
Are you making a proposal?  It sounds like you might be implying that it
would be better if some central infrastructure group could make all the
distributions?

As a developer of a Python package, I don't see how this would be better.
The developer would still have to get their software into some kind of
uniform configuration, so the central authority could package it.  You've
moved the problem from, "everyone has to make wheels" to "everyone has to
make a tree that's structured properly."  But if we can do the second
thing, the first thing is really easy.

Maybe I've misunderstood?

--Ned.

[toc] | [prev] | [next] | [standalone]

#96121

On 06.09.2015 22:06, Ned Batchelder wrote:
> As a developer of a Python package, I don't see how this would be better.
> The developer would still have to get their software into some kind of
> uniform configuration, so the central authority could package it.  You've
> moved the problem from, "everyone has to make wheels" to "everyone has to
> make a tree that's structured properly."  But if we can do the second
> thing, the first thing is really easy.
Unfortunately, I disagree with you one that and others already gave 
explanations why.


Internally, we had this "wild-west" tree in our source as well but we 
moved on to a properly structured tree and it solved problems we didn't 
even imagine to have solved when starting this effort some years ago.


Best,
Sven

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web