On Fri, May 13, 2016 at 11:22 AM, Brett Cannon wrote:
> No need to think; the decision is made and it's TOML. I know Chris doesn't
> mean to stir up trouble,
>
I got a bit out of sync with the conversation -- sorry for the noise.
-CHB
--
Christopher Barker, Ph.D.
Oceanographer
Emergency
On Fri, May 13, 2016 at 1:09 PM, Nathaniel Smith wrote:
> But, the plan *is* to make wheels the standard way to build packages --
> that will be in the next pep :-). I'm not sure I'd call it "lock down",
> because there's nothing that will stop you running setup.py bdist_rpm or
> whatever. But ou
On May 13, 2016 11:34 AM, "Chris Barker" wrote:
>
> One other question:
>
> Is it just examples or is "build" being defined as "build a wheel"?
>
> i.e. there are times one might want to build a package without building a
wheel -- just it install it yourself, or to put it in another package
format
On Fri, 13 May 2016 at 11:34 Chris Barker wrote:
> One other question:
>
> Is it just examples or is "build" being defined as "build a wheel"?
>
Just an example (clarified previously).
-Brett
>
> i.e. there are times one might want to build a package without building a
> wheel -- just it inst
One other question:
Is it just examples or is "build" being defined as "build a wheel"?
i.e. there are times one might want to build a package without building a
wheel -- just it install it yourself, or to put it in another package
format -- conda, rpm, what have you.
In conda's case, building a
On Fri, 13 May 2016 at 10:47 Paul Moore wrote:
> On 13 May 2016 at 18:15, Chris Barker wrote:
> > I think we're freaking out way too much about what *could* go wrong.
>
> It's more that:pip would have to vendor pyyaml, and it's not small. I
> have no idea whether it's easy to vendor, either (doe
On Fri, May 13, 2016 at 10:15 AM, Chris Barker wrote:
> On Tue, May 10, 2016 at 1:54 AM, Paul Moore wrote:
>>
>> I would love to use YAML. I really would. But for pip, we need a
>> robust, easy to vendor Python implementation
>
>
> conda has been using yaml forever (with pyyaml) , and whatever pr
On 13 May 2016 at 18:15, Chris Barker wrote:
> I think we're freaking out way too much about what *could* go wrong.
It's more that:pip would have to vendor pyyaml, and it's not small. I
have no idea whether it's easy to vendor, either (does it have
separate code paths for Python 2 and 3? I don't
On Tue, May 10, 2016 at 1:54 AM, Paul Moore wrote:
> I would love to use YAML. I really would. But for pip, we need a
> robust, easy to vendor Python implementation
conda has been using yaml forever (with pyyaml) , and whatever problem is
has (and there are many), I don't think I've ever seen a
devpi-server-4.0: fixing the pip-8.1.2 problem / PEP503 compliance
We've made available critically important releases of the devpi private
packaging
available. If you are not using "devpi" yet then you can may just read
On Thu, 12 May 2016 at 20:52 Nick Coghlan wrote:
> On 13 May 2016 at 02:33, Brett Cannon wrote:
> > Both Donald and Nathaniel say to drop it, and since I put it in just to
> be
> > overly cautious I'm fine with dropping it. So unless Nick says
> > "semantics-version or death!", I agree w/ my co-
On Thu, May 12, 2016 at 5:40 PM, Phil Thompson
wrote:
> I may be doing something wrong, but...
>
> The METADATA in my wheel uses Obsoletes but pip does not remove the obsoleted
> package on an install of my wheel.
>
> Is it supposed to?
No.
Unlike some other package managers, pip doesn't keep t
12 matches
Mail list logo
