Feel free to contact us if you
have any questions, concerns or suggestions.
--
Lindsey Heagy and Matthias Bussonnier for the SciPy organizers.
scipyb...@gmail.com
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/ma
y if they can't upgrade pip.
--
Matthias
On Mon, Nov 13, 2017 at 1:33 PM, Nathaniel Smith wrote:
> On Nov 13, 2017 12:03, "Gael Varoquaux"
> wrote:
>
> On Mon, Nov 13, 2017 at 10:26:31AM -0800, Matthias Bussonnier wrote:
>> This behavior is "new" (Nov/De
On Mon, Nov 13, 2017 at 10:31 AM, Stefan van der Walt
wrote:
>
> Is this documented anywhere? I couldn't find it via Google, and suspect
> it may be widely useful in the next few months.
Everything you need to know is on the Python3Statement practicality page:
http://www.python3statement.org/pr
> If a wheel is not available for the client platform, pip will try to install
> the latest version of the source distribution (.tar.gz or .zip) which I think
> is the cause of the problem here.
Unless the sdist is tagged with require_python and users have
recent-enough pip. Which is what was re
only) and 5.x (Python2+3) of IPython for about a year now.
--
M
On Mon, Nov 13, 2017 at 10:08 AM, Robert McLeod wrote:
>
>
> On Mon, Nov 13, 2017 at 7:47 AM, Matthias Bussonnier
> wrote:
>>
>> > For this to be efficient, it should be done soon enough to allow
>&
> For this to be efficient, it should be done soon enough to allow downstream
> projects to adapt their requirements.txt.
> Release managers: how much more effort would it be to upload current numpy to
> both numpy and numpylts?
I'm not quite sure I see the point. you would ask downstream to cha
'pip install ... will' to 'pip install ... should' especially for 2.7 users
it's rarer to have an up to date enough pip (9+) to respect the
requires_python metadata.
A mention to the py3statement would be appreciated :-) especially if you
decide to sign it.
You might want to also be a bit more po
Hi all,
Apologies if this mail appear out of thread I just subscribed to respond.
> Yeah, agreed. I don't feel like this is incompatible with the spirit of
> python3statement.org, though looking at the text I can see how it's not clear.
> My guess is they'd be happy to adjust the text, especially
