Do we have a minimum / maximum IPython version? #724
Comments
|
People installing Anaconda are going to get IPython 2. For most practical purposes it works the same as IPython 1, but there is the difference of the modal interface and the file system browser. I expect a student running IPython 1 in a workshop would be fine, so we could stick with that as a minimum version maybe until IPython 3 comes out. |
|
On Thu, Sep 18, 2014 at 11:29:40AM -0700, Matt Davis wrote:
Are our filled-in notebooks compatible with both the 1.x and 2.x |
|
I just did a quick check of opening a 2.2 made notebook with IPython 1.1 and it worked fine. There were some new features in IPython 2 like notebook signing and the idea of "trusted" notebooks, but the format seems to be compatible with IPython 1. |
|
On Thu, Sep 18, 2014 at 12:40 PM, Matt Davis [email protected] wrote:
That is correct. |
|
On Thu, Sep 18, 2014 at 11:40:04AM -0700, Matt Davis wrote:
So maybe I should bump the minimum version in |
|
On Thu, Sep 18, 2014 at 1:09 PM, W. Trevor King
+1 |
|
Sounds reasonable. |
|
On Thu, Sep 18, 2014 at 12:08:36PM -0700, W. Trevor King wrote:
Do we want to mention this range of versions in the install |
|
I wouldn't want it in the main installation instructions since we tell everyone to install Anaconda. Separate version notes for every package we use would get unwieldy. Maybe just a pointer to the checking script for people who want to verify existing installations? |
|
On Thu, Sep 18, 2014 at 01:17:47PM -0700, Matt Davis wrote:
Yeah, sounds good. |
|
@jiffyclub, can you comment on this? Your IPython-fu is much greater |
|
I did, think we're good. 😸 |
|
Can this one be closed? |
|
On Tue, Sep 30, 2014 at 11:15:04AM -0700, Greg Wilson wrote:
I haven't bumped the test script yet 1. |
|
On Tue, Sep 30, 2014 at 11:19:43AM -0700, W. Trevor King wrote:
Ok, I've bumped the test script [1](and updated the namespaced [2] $ git pull --log git://tremily.us/swc-setup-installation-test.git bc-namespaced if you do. |
I see the README recommends IPython >= 1.0 [1], but this script was only looking for >= 0.13. The busy bees at IPython have recently cut 2.3.0 (2014-10-01 [2]). IPython 2.x has a bunch of changes including deprecating the file/ prefix for local files [3] and adding a modal interface [4]. I asked for feedback on what versions we were supporting, and got this from Matt [5]: On Thu, Sep 18, 2014 at 11:40:04AM -0700, Matt Davis wrote: > I just did a quick check of opening a 2.2 made notebook with IPython > 1.1 and it worked fine. There were some new features in IPython 2 > like notebook signing and the idea of "trusted" notebooks, but the > format seems to be compatible with IPython 1. So this commit bumps the minimum version to 1.0. We'll revisit this compatibility after the IPython folks cut 3.0. [1]: https://github.com/swcarpentry/bc/blob/v2014.06/README.md#faq [2]: https://pypi.python.org/pypi/ipython/2.3.0 [3]: http://ipython.org/ipython-doc/dev/whatsnew/version2.0.html#directory-navigation [4]: http://ipython.org/ipython-doc/dev/whatsnew/version2.0.html#modal-user-interface [5]: swcarpentry/DEPRECATED-bc#724 (comment)
…ions
With [1], we can mostly point folks to the right place if we can't
find a particular package.
There's some funkiness around editors, since most of our editor
instructions are just links to the upstream projects, and we have
different suggestions for each operating system.
We're also pointing most users at Anaconda, instead of listing the
packages we need explicitly [2,3,4], it's hard to know which specific
PythonPackageDependencies should also link to #python-{system}. I've
left them off entirely for now, but instructors who want to link to
their setup instructions when we can get a Python version but not, for
example, a NumPy version should add a ('numpy', 'python') entry to the
check/check_id loop.
[1]: carpentries/workshop-template#171
[2]: swcarpentry/DEPRECATED-bc#724 (comment)
[3]: swcarpentry/DEPRECATED-bc#724 (comment)
[4]: swcarpentry/DEPRECATED-bc#724 (comment)
I see the README recommends IPython >= 1.0, but the check-script is still only looking for >= 0.13. I just noticed that the busy bees at IPython have recently cut 2.2.0. IPython 2.x has a bunch of changes including deprecating the
file/prefix for local files and adding a modal interface. Are we just trying to keep up with the most recent version? Are we even supporting the most recent versions? If we're supporting a range of versions, what's the range? I don't know if we have a policy for this yet, but I think we should have one soon.The text was updated successfully, but these errors were encountered: