ok, project is initialized (thanks kevin) and a tentative TOC is in place,
enough at least to get the various players to start making pull requests
for the portions they own or have expertise in.
see here: https://python-meta-packaging.readthedocs.org/en/latest/#
P.S. Kevin, I guess follow the
On Mar 16, 2013, at 5:06 PM, Daniel Holth dho...@gmail.com wrote:
Earlier today we merged the existing wheel branch into mainline pip.
This adds opt-in wheel install support (built into pip, pip install
--use-wheel ...) and the convenient pip wheel ... command for
creating the wheels you
On 18 March 2013 09:08, Glyph gl...@twistedmatrix.com wrote:
My understanding is that in order to achieve this nirvana, what we must do
is:
(Daniel may wish to chime in with more details)
A twisted developer, on each supported Windows configuration, must 'pip
install wheel; pip wheel
On Sun, Mar 17, 2013 at 8:38 PM, Marcus Smith qwc...@gmail.com wrote:
the pip docs have a cookbook entry now for the wheel support
http://www.pip-installer.org/en/latest/cookbook.html#building-and-installing-wheels
the usage reference is up to date as well
Hi all
I just joined up after the various discussions at PyCon and wanted to say hi.
(If you were also there and want to put a face/voice to the name, I did the
Visual Studio demo at one of the lightning talks.)
The main reason I want to get involved is the openly acknowledged lack of
Windows
On Fri, Mar 15, 2013 at 2:46 PM, Giulio Genovese
giulio.genov...@gmail.com wrote:
sudo pip-3.2 install --upgrade distribute
I get this:
File setuptools/dist.py, line 103
except ValueError, e:
You can't upgrade distribute with pip under Python 3. This is a known problem.
On 2013-03-18 16:34:25 +, Steve Dower said:
Hi all
I just joined up after the various discussions at PyCon and wanted to
say hi. (If you were also there and want to put a face/voice to the
name, I did the Visual Studio demo at one of the lightning talks.)
The main reason I want to
pkg_resources.requires() is our only current solution for parallel
installation of incompatible versions. This can be made to work and is
a lot better than the nothing we had before it was created, but also
has quite a few issues (and it can be a nightmare to debug when it
goes wrong).
Based on
I still think it is unfortunate that we are starting to extend pip to
be a tool for developers to create distributions. It would be better
of pip was kept as an install tool, and we added the utilities for
creating distributions separate.
I understand where you're coming from, but a few
On Mon, Mar 18, 2013 at 9:34 AM, Steve Dower steve.do...@microsoft.com wrote:
I expect I’ll mainly be lurking until I can be useful, which is why I wanted
to start with this post. I’m pretty good with Windows, and I have direct
access to all the experts and internal mailing lists. So just shout
On Mon, Mar 18, 2013 at 3:13 PM, Marcus Smith qwc...@gmail.com wrote:
The other option is of course that we start adding all sorts of
development commands to pip, such as build, test, sdist etc. But I do
think it's the wrong place.
I've thought of that too, but that's a discussion for
On 3/18/2013 5:16 PM, Lennart Regebro wrote:
On Sat, Mar 16, 2013 at 5:06 PM, Daniel Holth dho...@gmail.com wrote:
Earlier today we merged the existing wheel branch into mainline pip.
This adds opt-in wheel install support (built into pip, pip install
--use-wheel ...) and the convenient pip
On Mon, Mar 18, 2013 at 3:51 PM, Eric V. Smith e...@trueblade.com wrote:
On 3/18/2013 5:16 PM, Lennart Regebro wrote:
On Sat, Mar 16, 2013 at 5:06 PM, Daniel Holth dho...@gmail.com wrote:
Earlier today we merged the existing wheel branch into mainline pip.
This adds opt-in wheel install
On Mar 18, 2013, at 02:16 PM, Lennart Regebro wrote:
I still think it is unfortunate that we are starting to extend pip to
be a tool for developers to create distributions. It would be better
of pip was kept as an install tool, and we added the utilities for
creating distributions separate.
+1.
On Mar 18, 2013, at 04:13 PM, Nick Coghlan wrote:
Eventually I expect pip will grow a --wheel-only option to run it in
strict installer only mode, but the ecosystem is a long way from
supporting that being a useful option (especially since there are some
cases which will still require falling
On Mar 18, 2013, at 7:39 PM, Barry Warsaw ba...@python.org wrote:
On Mar 18, 2013, at 04:13 PM, Nick Coghlan wrote:
Eventually I expect pip will grow a --wheel-only option to run it in
strict installer only mode, but the ecosystem is a long way from
supporting that being a useful option
On Mon, Mar 18, 2013 at 3:13 PM, Marcus Smith qwc...@gmail.com wrote:
1) pip is *currently* very much a build tool in that it build/installs from
source archives, but I understand the new model is for pip to eventually be
working with pre-built wheels much of the time, with no build system
On Mon, Mar 18, 2013 at 4:39 PM, Barry Warsaw ba...@python.org wrote:
On Mar 18, 2013, at 04:13 PM, Nick Coghlan wrote:
Eventually I expect pip will grow a --wheel-only option to run it in
strict installer only mode, but the ecosystem is a long way from
supporting that being a useful option
On Mon, Mar 18, 2013 at 4:48 PM, Lennart Regebro rege...@gmail.com wrote:
On Mon, Mar 18, 2013 at 3:13 PM, Marcus Smith qwc...@gmail.com wrote:
1) pip is *currently* very much a build tool in that it build/installs from
source archives, but I understand the new model is for pip to eventually be
I do understand the confusion. Binary package formats have more than
one use. Coincidentally we have implemented the slightly different
cache compiles and distribute software features using the same
format. It might help if you can imagine that pip wheel produces a
different format than python
On Mon, Mar 18, 2013 at 5:28 PM, Daniel Holth dho...@gmail.com wrote:
I do understand the confusion. Binary package formats have more than
one use. Coincidentally we have implemented the slightly different
cache compiles and distribute software features using the same
format. It might help if
21 matches
Mail list logo
