On Thu, Jan 28, 2016 at 4:28 PM, Chris Barker wrote:
[...]
> Source in /tmp/pip-umxsOD-build has version 3.0.3, which satisfies
> requirement gsw==3.0.3 from
> file:///Users/chris.barker/miniconda2/conda-bld/work/gsw-3.0.3
>
> Requirement already satisfied (use --upgrade to upgrade): gsw==3.0.
On Thu, Jan 28, 2016 at 2:35 AM, Oscar Benjamin
wrote:
> On 28 January 2016 at 07:46, Nathaniel Smith wrote:
>>
>> On further thought, I realized that it actually has to be in the
>> standard library directory / namespace, and can't live in
>> site-packages: for the correct semantics it needs to
The pip wheel cache is in ~/Library/Caches/pip/wheels (OS X) or
~/.cache/pip/wheels (Linux). I'm not sure about Windows. You might have
some luck deleting files from there.
-Robert
On Thu, Jan 28, 2016 at 4:28 PM, Chris Barker wrote:
> Context:
>
> I'm maintaining a number of conda packages of
Context:
I'm maintaining a number of conda packages of various packages, some of
which are mine, some others, some pure python, some extensions, etc.
The way conda build works is you specify some meta data, and a build
script(s), and conda:
sets up an isolated environment in which to build.
in
On 28 January 2016 at 07:46, Nathaniel Smith wrote:
>
> On further thought, I realized that it actually has to be in the
> standard library directory / namespace, and can't live in
> site-packages: for the correct semantics it needs to be inherited by
> virtualenvs; if it isn't then we'll see conf
On 27 January 2016 at 22:54, Nick Coghlan wrote:
> I followed this up with the ABI folks, and the problem is that the
> elfutils in even DTS 2 is too old to support building libabigail, and
> later versions of the developer toolset (3 & 4) don't support being
> run on CentOS 5.
>
> However, even i
