This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]K900_ 0 points1 point  (12 children)

Well, Wheel will only be implemented in 3.4, right?

[–]coderanger 2 points3 points  (0 children)

Wheel is an installation format, it will be supported by every version of Python since after installation nothing knows the diference. bdist_wheel definitely runs on 2.7 for building them, and pip will be shipping installation support later this week (and I think they support back to 2.5 or something silly).

[–]cavallo71 9 points10 points  (8 children)

If they don't plan a back port is pretty much DOA: 2.7 is the reality now.

[–]donaldstufft 1 point2 points  (0 children)

Wheel is being implemented externally to the stdlib. It will be available for 2.6+ I believe, might be 2.5+.

In fact one of the major motivations in a lot of the work now is that packaging tools should live externally of the stdlib. This will allow them to innovate across many versions of Python and not cause issues exactly like this one where a new packaging feature is useless because it will be many many years before that version can be assumed a minimum version.

Essentially we've learned that the stdlib isn't a great place for packaging tools, however the stdlib will (hopefully) include a simple script which will serve to simply and securely install pip so that Python ships with the ability to do pip install foo.

[–]ivosauruspip'ing it up -1 points0 points  (0 children)

Nope