On 1 November 2017 at 02:23, Wes Turner wrote:
> Maybe the anaconda team has some insight on a standard way to capture (&
> configure) compiler versions and flags in package metadata?
The short answer is "You don't, and instead live with the related
uncertainty". Similar to Linux distro package
Yes, I know that. But unfortunately it's a legacy, so there is no way :(
I have resolved my issue with the following line in Dockerfile
RUN echo "[easy_install]\n\nindex-url = https://pypi.python.org/simple/"; >
~/.pydistutils.cfg
On Mon, Oct 30, 2017 at 3:21 PM, Marius Gedminas wrote:
> On Sa
Maybe the anaconda team has some insight on a standard way to capture (&
configure) compiler versions and flags in package metadata?
From
https://www.anaconda.com/blog/developer-blog/announcing-the-release-of-anaconda-distribution-5-0/
:
> The Anaconda 5.0 release used very modern compilers to re
On 31 October 2017 at 23:53, Nick Coghlan wrote:
> On 31 October 2017 at 22:49, Jeremy Stanley wrote:
>
>> On 2017-10-31 16:25:08 +1000 (+1000), Nick Coghlan wrote:
>> > Ideally we'd be recommending
>> > https://devpi.net/docs/devpi/devpi/stable/%2Bd/index.html to folks
>> looking
>> > to develo
Missed the fact that Nathaniel didn't quote the entire original message.
Here it is:
Generally, packages are compiled for the same processor generation as
the corresponding Python.
But not always -- e.g. NumPy opted for S
On 31 October 2017 at 22:49, Jeremy Stanley wrote:
> On 2017-10-31 16:25:08 +1000 (+1000), Nick Coghlan wrote:
> > Ideally we'd be recommending
> > https://devpi.net/docs/devpi/devpi/stable/%2Bd/index.html to folks
> looking
> > to develop a robust pre-release artifact testing workflow.
> >
> > W
On 2017-10-31 13:09:34 + (+), Thomas Kluyver wrote:
[...]
> If anyone wants to adapt the code to use in other tools, it's
> here:
>
> https://github.com/takluyver/flit/blob/ca08119/flit/inifile.py#L63-L108
[...]
Thanks for the pointer! That would make for a really great
stand-alone lintin
On 31 October 2017 at 22:13, Leonardo Rochael Almeida
wrote:
>
> Those are issues that buildout has solved long before pip was even around,
> but they rely on sys.path expansion that Ronny found objectionable due to
> performance issues.
>
The combination of network drives and lots of sys.path e
On Tue, Oct 31, 2017, at 12:49 PM, Jeremy Stanley wrote:
> Do the two share enough common code for successful uploading to a
> devpi instance to be indicative of whether PyPI will accept or
> reject on the grounds of, e.g., invalid trove classifiers (this one
> in particular has been the most commo
Forwarding here as suggested.
Forwarded Message
Subject:Re: [Python-ideas] Add processor generation to wheel metadata
Date: Mon, 30 Oct 2017 23:02:08 -0700
From: Nathaniel Smith
To: Ivan Pozdeev
CC: python-id...@python.org
On Mon, Oct 30, 2017 at 5:45 A
On 2017-10-31 16:25:08 +1000 (+1000), Nick Coghlan wrote:
> Ideally we'd be recommending
> https://devpi.net/docs/devpi/devpi/stable/%2Bd/index.html to folks looking
> to develop a robust pre-release artifact testing workflow.
>
> While we mention it a couple of times on packaging.python.org [1,2]
Hi,
On 31 October 2017 at 05:22, Nick Coghlan wrote:
> On 31 October 2017 at 05:16, RonnyPfannschmidt <
> opensou...@ronnypfannschmidt.de> wrote:
>
>> Hi everyone,
>>
>> since a while now various details of installing python packages in
>> virtualenvs caused me grief
>>
>> a) typically each tox
On Sat, Oct 28, 2017 at 12:22:32AM +0300, Alex Domoradov wrote:
> I got it. And what I should do with old system? For e.g. we still use ubuntu
> 12.04. Is there any way to upgrade pip/setuptools?
If you're using Ubuntu 12.04, then presumably you're paying Canoncial
for extended support, so ask the
On 31 October 2017 at 05:16, RonnyPfannschmidt <
opensou...@ronnypfannschmidt.de> wrote:
> Hi everyone,
>
> since a while now various details of installing python packages in
> virtualenvs caused me grief
>
> a) typically each tox folder in a project is massive, and has a lot of
> duplicate files,
14 matches
Mail list logo
