From bussonniermatthias at gmail.com Tue Apr 11 12:18:55 2017 From: bussonniermatthias at gmail.com (Matthias Bussonnier) Date: Tue, 11 Apr 2017 09:18:55 -0700 Subject: [IPython-dev] Released ipython 6.0.0rc1 Message-ID: Hi all, I just made a release of IPython 6.0.0 Rc1 yesterday. You can try with pip install ipython --upgrade --pre This version is Python 3 Only, but if you have a recent enough pip, you should automatically get the latest compatible with your system, that is to say 5.x which is still actively developed. See http://ipython.readthedocs.io/en/latest/whatsnew/version6.html for the what's new. -- Matthias From damianavila at gmail.com Wed Apr 12 09:56:03 2017 From: damianavila at gmail.com (=?UTF-8?Q?Dami=C3=A1n_Avila?=) Date: Wed, 12 Apr 2017 10:56:03 -0300 Subject: [IPython-dev] pdf slides from a Jupyter/IPython notebook using RISE In-Reply-To: References: Message-ID: Specifically for RISE, there have been some comments lately on this issue: https://github.com/damianavila/RISE/issues/127#issuecomment-289034824 I did not tested but it seems to be working. BTW, I hope to make to updates/enhancements soon to use the latest reveal.js that seems to be better at the pdf generation (several PRs on that topic merge lately). That should impact (and make better) the slides coming from nbconvert and also RISE. Cheers. 2017-03-20 14:24 GMT-03:00 Fernando Perez : > > On Mon, Mar 20, 2017 at 8:07 AM, Thomas Kluyver wrote: > >> You can try going into slideshow mode and then using the browser's print >> function. I think this has been a problem in the past, though, and I don't >> know if it's any better now. > > > Supposedly adding `?print-pdf` to the URL makes this possible, but I know > I and others have struggled with making it work reliably; e.g. > https://github.com/hakimel/reveal.js/issues/1252. Some more (old) > background is here: https://github.com/ipython/ipython/issues/3993. I > haven't tested recently, so I have no idea if it's any better. Would love > to hear if anyone has a reliable solution for this, coincidentally a > colleague was asking me about this very problem just a few days ago. > > Cheers > > f > -- > Fernando Perez (@fperez_org; http://fperez.org) > fperez.net-at-gmail: mailing lists only (I ignore this when swamped!) > fernando.perez-at-berkeley: contact me here for any direct mail > > _______________________________________________ > IPython-dev mailing list > IPython-dev at scipy.org > https://mail.scipy.org/mailman/listinfo/ipython-dev > > -- *Dami?n Avila* -------------- next part -------------- An HTML attachment was scrubbed... URL: From bussonniermatthias at gmail.com Wed Apr 19 18:41:11 2017 From: bussonniermatthias at gmail.com (Matthias Bussonnier) Date: Wed, 19 Apr 2017 15:41:11 -0700 Subject: [IPython-dev] IPython 6.0 released Message-ID: Hi all, We released ipython 6.0 about an hours ago. The conda builder are currently preheating, but in the bmeantime you can use PIP to install. This release is Python 3 only. See our blog post (https://blog.jupyter.org/2017/04/19/release-of-ipython-6-0/) and the release notes (http://ipython.readthedocs.io/en/stable/whatsnew/version6.html) $ pip install ipython --upgrade If you are on Python : Make sure you have pip 9 or above: $ pip --version $ pip install pip --upgrade Or pip **will upgrade** to an incompatible Python version . Reminder the IPython 5.x is LTS, is still compatible Python 2, and will still get upgrades. We should get 5.4 through the door soon hopefully (help welcome). Thanks everyone for your help Cheers, -- M From jason at jasongrout.org Wed Apr 19 19:45:58 2017 From: jason at jasongrout.org (Jason Grout) Date: Wed, 19 Apr 2017 23:45:58 +0000 Subject: [IPython-dev] IPython 6.0 released In-Reply-To: References: Message-ID: Congratulations! And our first python 3-only package! How long are we planning to support 5.x? Thanks, Jason On Wed, Apr 19, 2017 at 6:42 PM Matthias Bussonnier < bussonniermatthias at gmail.com> wrote: > Hi all, > > We released ipython 6.0 about an hours ago. > The conda builder are currently preheating, but in the bmeantime you > can use PIP to install. > > This release is Python 3 only. See our blog post > (https://blog.jupyter.org/2017/04/19/release-of-ipython-6-0/) and the > release notes ( > http://ipython.readthedocs.io/en/stable/whatsnew/version6.html) > > $ pip install ipython --upgrade > > If you are on Python : Make sure you have pip 9 or above: > > $ pip --version > $ pip install pip --upgrade > > Or pip **will upgrade** to an incompatible Python version . > > Reminder the IPython 5.x is LTS, is still compatible Python 2, and > will still get upgrades. > We should get 5.4 through the door soon hopefully (help welcome). > > Thanks everyone for your help > > Cheers, > -- > M > _______________________________________________ > IPython-dev mailing list > IPython-dev at python.org > https://mail.python.org/mailman/listinfo/ipython-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rgbkrk at gmail.com Wed Apr 19 20:03:28 2017 From: rgbkrk at gmail.com (Kyle Kelley) Date: Wed, 19 Apr 2017 17:03:28 -0700 Subject: [IPython-dev] IPython 6.0 released In-Reply-To: References: Message-ID: Woohoo IPython 6! Also Uh oh! I've duped myself into thinking that the IPython.display.display with updates was going to come to a Python 2 release. I was going to start doing deeper integration points into PySpark since the changes to ipykernel were out and useful (I've been using ip.display_pub.publish({ 'text/plain': 'Initial'}, transient={ "display_id": "here" })). On Wed, Apr 19, 2017 at 4:45 PM, Jason Grout wrote: > Congratulations! And our first python 3-only package! > > How long are we planning to support 5.x? > > Thanks, > > Jason > > > On Wed, Apr 19, 2017 at 6:42 PM Matthias Bussonnier < > bussonniermatthias at gmail.com> wrote: > >> Hi all, >> >> We released ipython 6.0 about an hours ago. >> The conda builder are currently preheating, but in the bmeantime you >> can use PIP to install. >> >> This release is Python 3 only. See our blog post >> (https://blog.jupyter.org/2017/04/19/release-of-ipython-6-0/) and the >> release notes (http://ipython.readthedocs.io/en/stable/whatsnew/ >> version6.html) >> >> $ pip install ipython --upgrade >> >> If you are on Python : Make sure you have pip 9 or above: >> >> $ pip --version >> $ pip install pip --upgrade >> >> Or pip **will upgrade** to an incompatible Python version . >> >> Reminder the IPython 5.x is LTS, is still compatible Python 2, and >> will still get upgrades. >> We should get 5.4 through the door soon hopefully (help welcome). >> >> Thanks everyone for your help >> >> Cheers, >> -- >> M >> _______________________________________________ >> IPython-dev mailing list >> IPython-dev at python.org >> https://mail.python.org/mailman/listinfo/ipython-dev >> > > _______________________________________________ > IPython-dev mailing list > IPython-dev at python.org > https://mail.python.org/mailman/listinfo/ipython-dev > > -- Kyle Kelley (@rgbkrk ; lambdaops.com) -------------- next part -------------- An HTML attachment was scrubbed... URL: From bussonniermatthias at gmail.com Wed Apr 19 20:07:04 2017 From: bussonniermatthias at gmail.com (Matthias Bussonnier) Date: Wed, 19 Apr 2017 17:07:04 -0700 Subject: [IPython-dev] IPython 6.0 released In-Reply-To: References: Message-ID: Hi Jason On Wed, Apr 19, 2017 at 4:45 PM, Jason Grout wrote: > Congratulations! And our first python 3-only package! JupyterHub was only Python 3 only :-) > How long are we planning to support 5.x? Our roadmaps says: June 2016 : Release IPython 5.0 LTS Traitlets "LTS" ipykernel LTS ipython_genutils LTS January 2017 : Release IPython 6.0 Python 3 only. July 2017 : Release Notebook 6.0 Python 3 only. December 2017: IPython 7.0 December 2017: End of active support IPython 5.x LTS July 2019 : Complete end of support for IPython 5.x from [here](https://github.com/jupyter/roadmap/blob/master/accepted/migration-to-python-3-only.md). I guess we are a bit late on Schedule, and technically we have 3 month to drop Python 2 from the notebook package , we can slide a bit, and we haven't decided IIRC if "No more support" means officially no support, or actually incompatible in the codebase. Also it's not because the **server** is Python 2 incompat that you can't run Python 2 kernels. -- M > > Thanks, > From fperez.net at gmail.com Fri Apr 21 17:49:32 2017 From: fperez.net at gmail.com (Fernando Perez) Date: Fri, 21 Apr 2017 14:49:32 -0700 Subject: [IPython-dev] IPython 6.0 released In-Reply-To: References: Message-ID: On Wed, Apr 19, 2017 at 3:41 PM, Matthias Bussonnier < bussonniermatthias at gmail.com> wrote: > Hi all, > > We released ipython 6.0 about an hours ago. > The conda builder are currently preheating, but in the bmeantime you > can use PIP to install. > > This release is Python 3 only. See our blog post > (https://blog.jupyter.org/2017/04/19/release-of-ipython-6-0/) and the > release notes (http://ipython.readthedocs.io/en/stable/whatsnew/ > version6.html) > Congratulations and a huge thanks to Matthias and everyone who continues to push on keeping IPyhton fresh and valuable for the community. I also want to highlight the value of that well-written, thoughtful blog post: it communicates very well the why and the how of our approach to the 2/3 transition, and I've already seen it being of value to other projects who are considering similar questions. Very best, f -------------- next part -------------- An HTML attachment was scrubbed... URL: From bussonniermatthias at gmail.com Fri Apr 21 18:05:51 2017 From: bussonniermatthias at gmail.com (Matthias Bussonnier) Date: Fri, 21 Apr 2017 15:05:51 -0700 Subject: [IPython-dev] IPython 6.0 released In-Reply-To: References: Message-ID: > Congratulations and a huge thanks to Matthias and everyone who continues to > push on keeping IPyhton fresh and valuable for the community. I also want > to highlight the value of that well-written, thoughtful blog post: it > communicates very well the why and the how of our approach to the 2/3 > transition, and I've already seen it being of value to other projects who > are considering similar questions. Thanks, I got a lot of help From Thomas and Mike that proofread several time and refactored some sections. So far we did not had any complaint that we were breaking things for Python 2 users (which so far is a good sign). And the usual Reddit and HN harsh comments were few. We got already a few bug reports where Jedi completion are less feature full than what people expect. And now "complaints" that `?`/`pinfo` does not do as much inference than :-D I'm going to preach a bit how to do a smooth transition at PyCon in about a month and detail a bit what we did upstream to allow this. I also hope to get some time to backport a couple of PR that have merge conflicts to the 5.x branch (if anyone want to help, look for close PRs with the "Still Need Manual Backport" tag), and hopefully get a 5.4 release soon. This will allow Python 2 / 5.x users to re-use readline. Cheers, -- M > > Very best, > > f > > _______________________________________________ > IPython-dev mailing list > IPython-dev at python.org > https://mail.python.org/mailman/listinfo/ipython-dev > From damianavila at gmail.com Sun Apr 23 08:37:46 2017 From: damianavila at gmail.com (=?UTF-8?Q?Dami=C3=A1n_Avila?=) Date: Sun, 23 Apr 2017 09:37:46 -0300 Subject: [IPython-dev] IPython 6.0 released In-Reply-To: References: Message-ID: A huge thanks to Matthias, Thomas and all the others contributing to this beautiful piece of the ecosystem. Cheers. 2017-04-21 19:05 GMT-03:00 Matthias Bussonnier : > > Congratulations and a huge thanks to Matthias and everyone who continues > to > > push on keeping IPyhton fresh and valuable for the community. I also > want > > to highlight the value of that well-written, thoughtful blog post: it > > communicates very well the why and the how of our approach to the 2/3 > > transition, and I've already seen it being of value to other projects who > > are considering similar questions. > > Thanks, I got a lot of help From Thomas and Mike that proofread several > time > and refactored some sections. So far we did not had any complaint that we > were > breaking things for Python 2 users (which so far is a good sign). And the > usual > Reddit and HN harsh comments were few. > > We got already a few bug reports where Jedi completion are less feature > full > than what people expect. And now "complaints" that `?`/`pinfo` does not do > as much inference than :-D > > I'm going to preach a bit how to do a smooth transition at PyCon in > about a month and detail a bit what we did upstream to allow this. I also > hope to get some time to backport a couple of PR that have merge > conflicts to the 5.x branch (if anyone want to help, look for close PRs > with > the "Still Need Manual Backport" tag), and hopefully get a 5.4 release > soon. > This will allow Python 2 / 5.x users to re-use readline. > > Cheers, > -- > M > > > > > Very best, > > > > f > > > > _______________________________________________ > > IPython-dev mailing list > > IPython-dev at python.org > > https://mail.python.org/mailman/listinfo/ipython-dev > > > _______________________________________________ > IPython-dev mailing list > IPython-dev at python.org > https://mail.python.org/mailman/listinfo/ipython-dev > -- *Dami?n Avila* -------------- next part -------------- An HTML attachment was scrubbed... URL: