Road to 6.0

We are closing in on 6.0 (I think). There are 35 open issues/PR targeted 6.0 and about 10 for 5.3. While usually we would stop working on 5.x after 6.0, 5.x is our LTS, so I don't want to block on it too much. Ie 5.3 can happen post 6.0 and we'll likely have a 5.4 and 5.5.

I'll use this as a meta issue to track the status of 6.0 release.

Completer API.

Notebook 5.0 is about to be released, so I don't see a point in refactoring Completion API to send extra info in metadata now. I think we can experiment with 5.1/Lab

Completer API is marked as unstable so we can still make changes afterward the old API has not been removed.

AFAICT, we have no more crashes with Jedi 0.10. I have pending PR to speed things up, but I doubt it's worth waiting for a 0.11 (we might want to bump to 0.10.1 though because of a messed up 0.10.tgz).

pip magic

Twitter is happy about it, but would like more. Do we ? Do we backport to 5.3 ?

Many issues can be bumped or are significant refactor.

I'm worried about the GeoJson display class. Which is relatively new. And whether is should be in core.

@JamiesHQ

cc @JamiesHQ , @willingc I'd like to have 6.0 out likely by mid March , at least be mid April to have it settled for PyCon.

Oh, a Big thing to be careful, this release if Python 3 only.

I've created a card on the release calendar: https://github.com/orgs/jupyter/projects/4

Just wanted to give you a heads up that the 6.0.0rc1 release is having a weird interaction with setuptools when unversioned ipython is a requirement - pypa/setuptools#1009 (even though pip still seems to do the right thing so far). I don't think this is anything you folks have control over, but I figure quite a few people will start hitting this soon.

I guess setuptools' dependency finding thing doesn't know about the requires-python metadata which handles avoiding the version for pip. As suggested on that issue, does it work if you try pip install -e . instead of python setup.py develop?

I guess the most practical way forwards is going to be to patch projects that require IPython to do something like this:

install_req = ['ipython']
if sys.version_info[0] < 3 and 'bdist_wheel' not in sys.argv:
    install_req.remove('ipython')
    install_req.append('ipython<6')

setup(
    ...
    install_requires=install_req
)

Yes I think you are correct. (And pip install does the right thing). Like I said, just wanted to give you a heads up.

…

On Tue, Apr 11, 2017 at 8:09 AM Thomas Kluyver ***@***.***> wrote: I guess setuptools' dependency finding thing doesn't know about the requires-python metadata which handles avoiding the version for pip. As suggested on that issue, does it work if you try pip install -e . instead of python setup.py develop? I guess the most practical way forwards is going to be to patch projects that require IPython to do something like this: install_req = ['ipython']if sys.version_info[0] < 3 and 'bdist_wheel' not in sys.argv: install_req.remove('ipython') install_req.append('ipython<6') setup( ... install_requires=install_req ) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#10329 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABhjqzqw8RNv-TfKBNtWvN8RF02e0zeTks5ru5fCgaJpZM4MJc8P> .

Thanks :-)

I'm going to start the release process of 6.0.

@Carreau

Ok, @Carreau has some issues with the github api but now we're back on track for the release schedule.

note to all others: if you ever are getting 401's even from https://api.github.com, check your .netrc because requests will look there and automatically append authentication headers to your requests & they might be out of date.

@takluyver

Strangely @takluyver appears to be the one uploading zip files to GitHub :-)
https://github.com/ipython/ipython/releases/tag/6.0.0

Released. Drafting the announcements.

Weird, I don't know how it got that.

👍 thanks for doing the release

Can SO update RTD and mark 6.0 as stable, I lost my PW and the reset link seem to not want to make its way my inbox.

Weird, I don't know how it got that

Hope your creds are not somewhere in the source tree.

I hope so too!

I've updated the 'stable' version on RTD to point to 6.0.0.

Cool thanks.

@mpacer

TODO:

BlogPost announce (@mpacer is on it)
Update IPython.org (I'm on it just need the blog post to be posted to get the URL, Update with IPython 6.0 release ipython-website#127)
Twitter
Mailing list
Conda forge in progress (Release IPython 6.0.0 conda-forge/ipython-feedstock#29)
PyPI done and 5.3 re-markes as still stable and unhidden.

Nice! ☀️

Navigation Menu

Road to 6.0 #10329

Completer API.

pip magic

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Road to 6.0 #10329

Description

Completer API.

pip magic

Activity

Carreau commented on Feb 24, 2017

Carreau commented on Feb 28, 2017

JamiesHQ commented on Mar 1, 2017

jtratner commented on Apr 11, 2017

takluyver commented on Apr 11, 2017

jtratner commented on Apr 11, 2017

takluyver commented on Apr 11, 2017

Carreau commented on Apr 19, 2017

mpacer commented on Apr 19, 2017

Carreau commented on Apr 19, 2017

Carreau commented on Apr 19, 2017

takluyver commented on Apr 19, 2017

takluyver commented on Apr 19, 2017

Carreau commented on Apr 19, 2017

takluyver commented on Apr 19, 2017

Carreau commented on Apr 19, 2017

Carreau commented on Apr 19, 2017

willingc commented on Apr 19, 2017

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions