On Wed, Nov 23, 2016 at 3:14 PM, Chris Barker wrote:
> On Wed, Nov 23, 2016 at 6:35 AM, Thomas Kluyver
> wrote:
>
>>
>> Questions:
>> 1. Editable installs. The PEP currenly specifies a hook to do an
>> editable install (like 'pip install -e' or
I wouldn't be afraid of editable installs. They are trivial and involve
building the package in place and putting a .pth file where it will be
noticed. Specify editable packages can't necessarily be uninstalled in a
standard way and you are done.
The bespoke build tool tells pip where the package
On Wed, Nov 23, 2016 at 6:35 AM, Thomas Kluyver
wrote:
> Questions:
> 1. Editable installs. The PEP currenly specifies a hook to do an
> editable install (like 'pip install -e' or 'setup.py develop') into a
> given prefix. I don't think that specifying a prefix is
On 23 November 2016 at 19:17, Brett Cannon wrote:
> My vote is for 1c (easier to add 1a later), and dashes (for some reason I
> just like how they look more in config files).
I agree, 1c sounds like a reasonable starting place (but I don't tend
to use editable installs, so
Hi,
On Wed, Nov 23, 2016 at 6:35 AM, Thomas Kluyver wrote:
> I'd like to push PEP 517 forwards again. This PEP specifies a general
> build system interface so that a source tree can specify a tool (such as
> flit), and pip can ask that tool to generate a wheel. This would
This then ties into Kenneth's pipfile idea he's working on as it then makes
sense to make a wagon/wheelhouse for a lock file. To also tie into the
container aspect, if you dev on Windows but deploy to Linux, this can allow
for gathering your dependencies locally for Linux on your Windows box and
Thanks for starting this up again!
My vote is for 1c (easier to add 1a later), and dashes (for some reason I
just like how they look more in config files).
On Wed, Nov 23, 2016, 06:36 Thomas Kluyver, wrote:
> I'd like to push PEP 517 forwards again. This PEP specifies a
I'd like to push PEP 517 forwards again. This PEP specifies a general
build system interface so that a source tree can specify a tool (such as
flit), and pip can ask that tool to generate a wheel. This would allow
us to install from an sdist or a VCS checkout without running a setup.py
file.