Giter VIP home page Giter VIP logo

jupyter's Introduction

Jupyter

Read this in other languages: English, Español, Português, Français

Jupyter metapackage for installation and documents

Documentation structure

This documentation uses the Sphinx documentation engine.

The documentation is located in the docs/source folder. When you build the documentation, it will be placed in the docs/build folder. It is written in a combination of reStructuredText and MyST Markdown.

Build the documentation locally

There are a few ways to build the documentation; see below for instructions:

Build the documentation automatically with nox

The easiest way to build the documentation locally is by using the nox command line tool. This tool makes it easy to automate commands in a repository, and we have included a docs command to quickly install the dependencies and build the documentation.

To build and preview the site locally, follow these steps:

  1. Clone this repository.

    $ git clone https://github.com/jupyter/jupyter
    $ cd jupyter
  2. Install nox

    $ pip install nox
  3. Run the docs command

    $ nox -s docs

This will install the needed dependencies in a virtual environment using pip. It will then place the documentation in the docs/build/html folder. You may explore these HTML files in order to preview the site.

Create a live server to automatically preview changes

There is another nox command that will do the above, and also create a live server that watches your source files for changes, and auto-builds the website any time a change is made.

To start this live server, use the following nox command:

$ nox -s docs-live

When the build is finished, go to the URL that is displayed. It should show a live preview of your documentation.

To stop serving the website, press Ctrl-C in your terminal

Build the documentation manually

To build the documentation manually, follow these steps:

First, install the miniconda Python distribution.

Next, navigate to the /docs directory and create a conda environment:

conda env create -f environment.yml

Activate the environment:

source activate jupyter_docs

Build the docs using Sphinx with the following commands:

make clean
make html

The docs will be built in build/html. They can be viewed by opening build/html/index.html or starting an HTTP server and navigating to 0.0.0.0:8000 in your web browser.

python3 -m http.server

Releasing the jupyter metapackage

Anyone with push access to this repo can make a release of the Jupyter metapackage (this happens very rarely). We use tbump to publish releases.

tbump updates version numbers and publishes the git tag of the version. Our GitHub Actions then build the releases and publish them to PyPI.

The steps involved:

  1. Install tbump: pip install tbump
  2. Tag and publish the release tbump $NEW_VERSION.

That's it!

jupyter's People

Contributors

ashleytqy avatar bl-ue avatar captainsafia avatar carreau avatar charnpreetsingh avatar choldgraf avatar ellisonbg avatar ericsnekbytes avatar filipefilardi avatar gadgetsteve avatar georgianaelena avatar isabela-pf avatar ivanov avatar jasonweill avatar jdfreder avatar jesusbibieca avatar jhermann avatar jzf2101 avatar krassowski avatar minrk avatar palewire avatar parente avatar parsing-science avatar rgbkrk avatar takluyver avatar tchajed avatar transifex-integration[bot] avatar willingc avatar yuvipanda avatar zsailer avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

jupyter's Issues

Install instructions for upgrading from IPython < 4

The install page should have some mention of how to upgrade from earlier versions of the notebook. I think this should be just a matter of installing the Jupyter package, but people will probably want some reassurance.

@asmeurer, have you thought about what the packaging will look like on conda? On PyPI, we'll have a jupyter metapackage that just depends on all of our other packages. It would be convenient if this pattern was the same in conda. Is there a mechanism to deprecate or rename the ipython-notebook package? In Debian packaging, I know it would become a 'transitional' package, expressing a dependency on its new name, for instance.

Extend logging capabilities

Hi,

Right now, Jupyter uses the traitlets logging capabilites to log to stdout. When hosting Jupyter as a service in the cloud, there might be a need to send logs to other systems (e.g. a system exposed via a REST endpoint). Would a PR to create a configurable extension point for logging capabilities be something that you would support?

Thanks!

Poor performance when saving a notebook over SSH

I use the jupyter notebook on a local Linux system (Ubuntu 15.10) and I run the sever and kernel on a remote Linux VPS (also Ubuntu) through an SSH connection. The server is Python 3.5 (Anaconda).

The connection upload speed is much slower than the download speed and I've noticed that the time to save a notebook is very long (several minutes).
The network connection upload rate spikes to about half the available bandwidth and the browser (Chrome 47) slows down so that normal browsing (for documentation for example) is also slowed down to the point of being unusable.

I use Bokeh plots in the notebook, and it is only when I have Bokeh plot output in the notebook that I've noticed that this occurs.

Could the notebook save function be also saving all the Bokeh plot output back through to the server?
That seems unnecessary to me.

Can anyone confirm that this is happening?

Add a Try Jupyter! section to the docs

As the docs are being restructured for 4.0, it may be helpful for novices that land on the docs via google or other searches to have a section that previews Jupyter without installing (like a developer would).

Perhaps just prior to Installation in Table of Contents, add a brief section:

Try Jupyter! (No installation necessary)

In a hurry to get started with Jupyter? Do you wish to try Jupyter before installing it to your system?

We want to share Jupyter with you, and we hope you will give it a try on our website https://try.jupyter.org

tryjupyter

If you wish to try Jupyter with your own notebook, click the upload button on the upper right to upload your ipynb notebook file.

Thanks to @jhamrick for the licecap recommendation. We've been adding gifs to nbgrader docs, and I think it helps with reinforcing the written docs.

Check and update documentation and potentially stale info about Docker images

While this is about Docker and arguably could have been filed in our docker repo, I think it's worth putting it here as our main "docs central" should always be a good place for folks to find their bearings.

This blog post by @GrahamDumpleton has some good notes and details from a user's perspective on his experiences setting up our Docker images and finding info about them.

We should go over this post and ensure that any possible dead-ends he identifies can be improved (such as, for deprecated images, pointing out where users should look instead, so they don't feel like they hit a dead end).

Pinging @willingc as you might be able to put this on your radar, and thanks to @ctb for bringing it to my attention.

Incorrect CORS blocking

The CORS implementation interferes with this chrome extension:
Allow-Control-Allow-Origin
This extension stops chrome from enforcing CORS rules, and is used by many developers.

I get this message in the log:

Blocking Cross Origin API request.  Origin: http://evil.com/, Host: 192.168.1.185:8888

Jupyter works fine in a browser profile without that extension, but with the extension (even disabled for the tab) it fails.

Fix broken docs link.

Pandas rebase link is in fact: https://github.com/pydata/pandas/wiki/Git-Workflows#user-content-git-rebase and continuum download as a permanent redirect with www prepended.

Markdown syntax imcompatibility (headings) with IPython 3.x created notebooks

Notebooks that were created in IPython 3.x have there Markdown cells not properly shown in Jupyter 4.0. At least this goes for headings. After a small investigation it appears that the Markdown syntax has slightly changed.
In IPython 3.x, the following showed up properly as a heading level 1 in a Markdown cell in a notebook:
#Heading level 1
In Jupyter 4.0, a space needs to be added after the hashtag to make it work:
# Heading level 1

Implementing a more robust issue/PR tagging system

Proposal

As I've been working on improving the contribution documentation, I realize that we can benefit greatly from implementing a tagging system on our issues and our PRs. I imagine that on on each issue or PR we would have the following tags.

  1. A tag representing whether the issue related to a front-end (Javascript/CSS), backend (Python), or documentation problem.
  2. A tag representing the difficulty level of submitting a PR on that issue. We can determine difficulty using some of these metrics.
    • The amount of Jupyter related knowledge needed to submit a PR on this
    • The amount of Javascript/Python/CSS knowledge needed to submit a PR on this
    • Other metrics probably
  3. A tag representing the effort level to submit a PR for particular issue. I imagine the following divisions being issued on this.
    • easy — issues that can be knocked down in a couple of hours of work by a semi-experienced developer, very similar to the sprint-friendly tag that we use now
    • medium — issues that require a bit more time than the easy level issues and are for beginners or semi-frequent contributors who want a challenge
    • hard — issues that are probably best addressed by someone who has a lot of experience with the code base

In line with this, I think we should avoid using the sprint-friendly tag to represent issues that are easy to tackle. If I am a new contributor, I don't really understand what sprint-friendly means in the context of difficulty but a tag like difficulty: easy is much easier to understand.

There is room for more tags to be included but I think the three below cover the basics.

There are some pros and cons to implementing this tagging system as outlined below.

Cons

  • More time has to be dedicated to organizing and tagging issues from the owners of each repo
  • It would be difficult to maintain consistency in the way that we tag difficulty an effort level as it depends on the person tagging

Pros

  • It shows new contributors (and existing ones) that we care about making the issues approachable for them
  • It will help us figure out how we are allocating our manpower (for example, is Safia taking too many of the easy issues when she can tackle some more difficult ones? Should Steve focus on front-end issues while Bob focuses on back-end?) so that we can work through things more efficiently
  • Will help first time contributors (and existing ones) navigate the issues and hopefully increase the amount of community contributions

And I'm sure there are other pros and cons but I can't think of them at the moment. I'm welcome to hearing them though!

EDIT: Added a pro

cc/ @minrk @Carreau @ellisonbg @fperez or anyone else who should be included in the discussion

fatal error in launcher

Windows 7
Python installation path: C:\Program Files (x86)\Python27\

When I:
C:\Program Files (x86)\Python27>jupyter notebook

I get:
Fatal error in launcher: Unable to create process using '""C:\Program Files (x86)\Python27\python.exe"" "C:\Progra~2\Python27\Scripts\jupyter.exe" notebook'

The jupyter*.exe files under C:\Program Files (x86)\Python27\Scripts have the "path with spaces" embedded.

I had a similar problem with pip but a ~recent update solved that.

How can I solve it for jupyter?

Jupyter Desktop App

Since it looks like Jupyter/iPython has stabilized, perhaps this project or a variant can be (re)started. I think it would be quite useful and a huge step for user-friendliness to not have to interact with the CLI + a browser for the notebooks. Making it cross-platform seems doable using node-webkit or electron (is there a good Python alternative?).

With Jupyter, it also seems possible to decouple the desktop app from a specific kernel, so the same desktop app could be used for all the supported languages (?).

It probably makes sense to pool our efforts if others are interested in this.

@mangecoeur what do you think?

Jupyter should make a .exe on Windows

After installing Jupyter on Windows it seems the "jupyter" command isn't turned into an executable, and thus can't be run through the windows command line. It creates a jupyter file containing:

#!C:\Python34\python.exe
"""Launch the root jupyter command"""

from jupyter_core.command import main

if __name__ == '__main__':
    main()

But obviously this cant be run on Windows without doing C:\python\python.exe C:\python\scripts\jupyter --help, which is not as nice as just jupyter

Output do not update after close and reopen the notebook page

Hi,

I am using a library named keras with jupyter notebook. It's nice that keras use a text progress bar to indicate the progress like this:

Train on 381734 samples, validate on 20092 samples
Epoch 1/1
381734/381734 [==============================] - 257s - loss: 0.4094 - val_loss: 0.2863

But the problem is that, if the script is running with the progress bar, I can't close the webpage which I used to start the script. Otherwise I won't see the progress bar update anymore, when I open the notebook again, if it's still running, the title will become something like "(Starting) XXXXXX", but I can't see any update in the page.

The progress bar used by keras is like this:
https://github.com/fchollet/keras/blob/b126b6328a44fa3332d2d7fd011da3ff196a669a/keras/utils/generic_utils.py

Can anyone look into this?

Thanks in advance.

Add RTD link in each github repository

To facilitate discovering the docs, all the github repositories under the jupyter organization should have a link to the readthedocs documentation (when existent).

Preferably the link should be put in the "heading" next to the repository description, but also a simple link in the README would be enough.

For one, the "jupyter" repo should have a link to jupyter.readthedocs.org.

Fatal Error on boot: "parser.py"

Yesterday I encountered the silliest error.

I uninspiredly named the parser for my dataset "parser.py". When I tried to boot Jupyter from my working directory the kernel kept dying. I got the generic error message "unable to find BeautifulSoup" (XML, HTML, SGML) which as far as I was concerned might as well be used by Jupyter at some point in the parsing process.

Renaming the file obviously fixed the error, but it took me a while to figure out where it went wrong. I'm pretty sure I'm not the only uninspired programmer naming their parser "parser.py" though ;-).

Kernel hangs with latest jupyter 4.0.4

Installs and starts successfully. However, when I enter some Scala expression in the first cell and start it, it remains at "[*]" forever. Both for scala 2.10 and 2.11.

jupyter --version outputs to stderr

Why does --version write to stderr, rather than stdout? This is non-intuitive and not what ipython used to do! (This broke the IHaskell install :( )

Question: how to install Python 2.7 as an additional kernel next to the default Python 3.X one?

I am using Jupyterhub, but the amount of inconsistent documentation is not helping. All I want is a fully featured (numpy, scikit*, etc.) Jupyter server up and running, which I expect it what most people want.

The fact that there are three different projects: jupyterhub, jupyter, and ipython doesn't really help when every project sometimes refers to the documentation of the project they depend on.

[Docs] list supported mimetype

Put a list of mimetype and explain the particular case of mathJax. tex/latex.

I know it is notebook specific, but I think there should at least be a reference in the main docs. (or do we put that link in jupyter_client ?)

Anyway for background see thread on jupyter ML

When including gists every row in the output is divided by a solid line

I tried including a gist in my jupyter notebook and got the following output.

A markdown cell:

<script src="https://gist.github.com/KobaKhit/45846b81ee8b28363b4a.js"></script>

Output:
screen shot 2015-12-03 at 9 44 41 pm

As you can see every row is divided by a solid line. It would be nice to be able to include gists without those solid lines. Thanks.

Notebook guide for beginners

I'm opening this issue to follow-up a recent discussion on ipython-dev (thread).

Briefly, I think there is the need for a concise documentation for absolute beginners that receive a notebook and need to run it. My main use-case is the notebook-as-an-app in which we provide notebooks as mini-apps to perform a single task. The user needs only to know how to run it and change a few parameters (i.e. input file name).

I had hard time finding docs for beginners so I started such a guide:

http://jupyter-notebook-beginner-guide.readthedocs.org/

and @Carreau suggested to open an issue here to discuss possible integration with the official documentation.

[Idea] Add a glossary of Jupyter projects to docs

I was editing the docs to think about how to add a section on migrating from 3.x to 4.x. As I was reading the docs' landing page, there are a lot of projects now where there were far fewer before.

I think it would be helpful to new users to have an alphabetical glossary of all Jupyter projects (or related projects).

Show execution time

Show execution time script, like this

in[ ]: input code
out[ ]: output
34ms

This "34ms" is the execution time showed after the code runned.

Cannot make the Jupyter notebook work (Python kernel) on Windows 7

Hello,

First of all, thank you so much for all your hard work. Jupyter is just great!
However, I'm pulling out whatever hair I have left trying to make it work (the notebook part) on Windows. I've followed the instructions from http://jupyter.org/ to the letter, read the forums, did my best to make it work, but no luck.

My details are like:

  • Windows 7 Professional, 64 bit machine
  • tried Anaconda 64 bit or 32 bit, Python 2.7 or Python 3.5 (all possible combos)
  • all the other things (Ipython or the Jupyter QTConcole) work like a charm
  • every time I try a "jupyter notebook --debug" in the cmd window, I get errors. The notebook seems to work, but there is a broken link below the Python logo which reads " No Connection to Kernel". The errors (from the cmd window, in chronological order) are:
    • Terminals not available (error was No module named terminado) - that's easily solvable, I do a "conda install pip" and then a "pip install terminado"
    • Terminals not available (error was No module named termios) - that's where I hit the wall.

Thank you so much!

Possibly inaccurate shim warning message

I'm not sure in which repo to report this. In Jupyter 4.0.6, if I do:

import IPython.nbconvert

I get the following message:

Anaconda\envs\py3\lib\site-packages\IPython\nbconvert.py:13: 
ShimWarning: The `IPython.nbconvert` package has been deprecated. 
You should import from ipython_nbconvert instead.
  "You should import from ipython_nbconvert instead.", ShimWarning)

(manually added line break)

Shouldn't be nbconvert instead of ipython_nbconvert?

Also, any reason the message is ending with , ShimWarning)?

IPython is not a python package after installing jupyter directly on Windows

I have Python2.7 on my Windows. If I just install jupyter using

pip install jupyter

without ipython installed before, then the IPython directory has no __init__.py file so that it is not a valid package, and jupyter notebook fails.
If I install ipython first with

pip install ipython

then install jupyter, everything is fine with no problem.

Formatted docs for magic functions

I was looking for documentation for the 'magic' functions online, but the top hit on Google is a tutorial which briefly mentions some of them, and the next hit (which admittedly I only found now embarrassingly) looks right but is missing some - %autoindent, %cat and %clear for example aren't there, so it's hard to tell how old a version they are from (which probably explains why I didn't find them).

I did the %magic command to get the plaintext docs, and searched this to try and find any formatted copy online but there wasn't, so I went ahead and turned them into markdown.

e.g. searching the documentation for the %cat command shows the developer docs, but finds nothing in a readable format, nor anything 'all in one place'.

I get the feeling I may have wasted my time turning the 'man pages' produced by the %magic command into a markdown version, as it looks like even though that IPython list is outdated, it's processed the indenting in some way to properly format code blocks and regular <pre> elements within a <dl> definitions list — so I don't know if mine will actually be any use to you... 😅 was handy for me to read anyway

( Also this may relate to #20 for a subcommand to open formatted docs in a browser )

Failed to run

Hi!

I've been trying to use jupyter notebook, and when I type in a terminal:

sudo pip3 install jupyter it says:

Requirement already satisfied (use --upgrade to upgrade): jupyter in ./.local/lib/python3.5/site-packages
Cleaning up...

Then I type:

sudo pip3 install jupyter --upgrade
Requirement already up-to-date: jupyter in ./.local/lib/python3.5/site-packages
Cleaning up...

And then I try to run jupyter:

jupyter notebook
Traceback (most recent call last):
  File "/usr/local/bin/jupyter-notebook", line 7, in <module>
    from notebook.notebookapp import main
  File "/usr/local/lib/python2.7/dist-packages/notebook/notebookapp.py", line 28, in <module>
    from jinja2 import Environment, FileSystemLoader
  File "/usr/local/lib/python2.7/dist-packages/jinja2/__init__.py", line 33, in <module>
    from jinja2.environment import Environment, Template
  File "/usr/local/lib/python2.7/dist-packages/jinja2/environment.py", line 13, in <module>
    from jinja2 import nodes
  File "/usr/local/lib/python2.7/dist-packages/jinja2/nodes.py", line 19, in <module>
    from jinja2.utils import Markup
  File "/usr/local/lib/python2.7/dist-packages/jinja2/utils.py", line 531, in <module>
    from markupsafe import Markup, escape, soft_unicode
ImportError: No module named markupsafe

What can I do tu be able to run this??

Thank you so much!

open in windows without console window flashing

Is there a way to open jupyter without the console window flashing in windows? I've tried pythonw but tt flashes twice for me every time:

"C:\Program Files\Python34\pythonw.exe" -m qtconsole

Add additional installation paths

The existing install docs are great for getting a basic Jupyter Notebook environment locally. As we look to make it ever easier for users to walk-up and get a notebook environment with supporting tools for work in their favorite languages on their desktop or in the cloud, we should expand with further options. Some suggestions:

  1. Instructions or pointer to running docker-stacks in a VM locally (why: batteries included vs pip/conda install everything natively)
  2. Instructions on deploying single notebook instances to cloud providers (e.g., Rackspace, Softlayer, AWS, ...) (why: bigger machines, on compute clusters)

I'm glad to contribute over time here. Just writing the idea down for consideration.

Create a better way to manage subproject docs

@willingc has been thinking about how to manage the fact that the different Jupyter/IPython subprojects are in lots of repos. That presents a number of problems for users:

  • When they go between each RTD repo, they home icon in RTD changes its target.
  • Then TOC for the docs changes to that repo.
  • There isn't any easy way to get back to the global index.
  • There isn't an easy link to the jupyter.org or ipython.org home pages.

These things were made painfully clear in some of the users tests we ran.

I wanted to open an issue to use in discussing solutions to these problems.

Overall, I think we should start with the simplest thing possible, and test user test it to improve it.

I think the simplest thing would be to create a single Subproject index page that all of our RTD repos can manually have a copy of. This would allow us to focus on the visual and information design of a single page and have that replicated across our repos, without having to get into combining all the docs into a single repo or using git submodules.

Thoughts?

@minrk @takluyver @fperez

Shift-M does not work for merging cells

Shift-M does not work for merging cells. It used to work for me all the time, has something changed? I'm in command mode (esc). Sorry if this is a duplicate!

tab completion problem?

python version:3.4.3
jupyter version:4.0.6
system:mac os x ei 10.11

tab completion doesn't work totally when import any standard module. any can help?

Installing jupyter with conda also installs pip packages

When installing jupyter in a new env, it installs all the correct packages, but for some, it also installs pip packages:

jupyter-client            4.0.0                     <pip>
jupyter-console           4.0.1                     <pip>
jupyter-core              4.0.4                     <pip>
jupyter_client            4.0.0                    py27_0
jupyter_console           4.0.1                    py27_0
jupyter_core              4.0.4                    py27_0

If I then try to remove the pip installed packages to only have one version of each, I get the following message:

[test_jupyter] C:\Users\vdbosscj>pip uninstall jupyter-client
DEPRECATION: Uninstalling a distutils installed project (jupyter-client) has bee
n deprecated and will be removed in a future version. This is due to the fact th
at uninstalling a distutils project will only partially uninstall the project.
Uninstalling jupyter-client-4.0.0:
  c:\anaconda\envs\geo\lib\site-packages\jupyter_client-4.0.0-py3.4.egg-info
Proceed (y/n)? y
  Successfully uninstalled jupyter-client-4.0.0

Full output of creating the env and of conda list afterwards:

C:\Users\vdbosscj>conda create -n test_jupyter jupyter
Fetching package metadata: ....
Solving package specifications: .
Package plan for installation in environment C:\Anaconda\envs\test_jupyter:

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    jsonschema-2.4.0           |           py27_0          92 KB
    markupsafe-0.23            |           py27_0          23 KB
    mistune-0.7.1              |           py27_0         122 KB
    pygments-2.0.2             |           py27_0         1.1 MB
    pyqt-4.10.4                |           py27_1        31.2 MB
    pyreadline-2.0             |           py27_0         127 KB
    ssl_match_hostname-3.4.0.2 |           py27_0           6 KB
    jupyter_console-4.0.1      |           py27_0          62 KB
    ------------------------------------------------------------
                                           Total:        32.7 MB

The following NEW packages will be INSTALLED:

    certifi:            14.05.14-py27_0
    decorator:          4.0.2-py27_0
    ipykernel:          4.0.3-py27_0
    ipython:            4.0.0-py27_0
    ipython_genutils:   0.1.0-py27_0
    ipywidgets:         4.0.2-py27_0
    jinja2:             2.8-py27_0
    jsonschema:         2.4.0-py27_0
    jupyter:            1.0.0-py27_0
    jupyter_client:     4.0.0-py27_0
    jupyter_console:    4.0.1-py27_0
    jupyter_core:       4.0.4-py27_0
    markupsafe:         0.23-py27_0
    mistune:            0.7.1-py27_0
    nbconvert:          4.0.0-py27_0
    nbformat:           4.0.0-py27_0
    notebook:           4.0.4-py27_0
    path.py:            7.6-py27_0
    pickleshare:        0.5-py27_0
    pip:                7.1.2-py27_0
    pygments:           2.0.2-py27_0
    pyqt:               4.10.4-py27_1
    pyreadline:         2.0-py27_0
    python:             2.7.10-0
    pyzmq:              14.7.0-py27_0
    qtconsole:          4.0.1-py27_0
    setuptools:         18.1-py27_0
    simplegeneric:      0.8.1-py27_0
    ssl_match_hostname: 3.4.0.2-py27_0
    tornado:            4.2.1-py27_0
    traitlets:          4.0.0-py27_0
    wheel:              0.24.0-py27_0

Proceed ([y]/n)?

Fetching packages ...
jsonschema-2.4 100% |###############################| Time: 0:00:00 213.44 kB/s
markupsafe-0.2 100% |###############################| Time: 0:00:00 120.19 kB/s
mistune-0.7.1- 100% |###############################| Time: 0:00:00 206.90 kB/s
pygments-2.0.2 100% |###############################| Time: 0:00:03 325.80 kB/s
pyqt-4.10.4-py 100% |###############################| Time: 0:00:35 919.03 kB/s
pyreadline-2.0 100% |###############################| Time: 0:00:00 254.64 kB/s
ssl_match_host 100% |###############################| Time: 0:00:00   1.48 MB/s
jupyter_consol 100% |###############################| Time: 0:00:00 311.88 kB/s
Extracting packages ...
[      COMPLETE      ]|##################################################| 100%
Linking packages ...
[      COMPLETE      ]|##################################################| 100%
#
# To activate this environment, use:
# > activate test_jupyter
#

C:\Users\vdbosscj>activate test_jupyter
Activating environment "test_jupyter"...

[test_jupyter] C:\Users\vdbosscj>conda list
# packages in environment at C:\Anaconda\envs\test_jupyter:
#
backports.ssl-match-hostname 3.4.0.2                   <pip>
certifi                   14.05.14                 py27_0
decorator                 4.0.2                    py27_0
ipykernel                 4.0.3                    py27_0
ipython                   4.0.0                    py27_0
ipython-genutils          0.1.0                     <pip>
ipython_genutils          0.1.0                    py27_0
ipywidgets                4.0.2                    py27_0
jinja2                    2.8                      py27_0
jsonschema                2.4.0                    py27_0
jupyter                   1.0.0                    py27_0
jupyter-client            4.0.0                     <pip>
jupyter-console           4.0.1                     <pip>
jupyter-core              4.0.4                     <pip>
jupyter_client            4.0.0                    py27_0
jupyter_console           4.0.1                    py27_0
jupyter_core              4.0.4                    py27_0
markupsafe                0.23                     py27_0
mistune                   0.7.1                    py27_0
nbconvert                 4.0.0                    py27_0
nbformat                  4.0.0                    py27_0
notebook                  4.0.4                    py27_0
path.py                   7.6                      py27_0
pickleshare               0.5                      py27_0
pip                       7.1.2                    py27_0
pygments                  2.0.2                    py27_0
pyqt                      4.10.4                   py27_1
pyreadline                2.0                      py27_0
python                    2.7.10                        0
pyzmq                     14.7.0                   py27_0
qtconsole                 4.0.1                    py27_0
setuptools                18.1                     py27_0
simplegeneric             0.8.1                    py27_0
ssl_match_hostname        3.4.0.2                  py27_0
tornado                   4.2.1                    py27_0
traitlets                 4.0.0                    py27_0
wheel                     0.24.0                   py27_0

Art for Youtube channel

The youtube channel does not have a nice panoramic picture:

screen shot 2015-10-20 at 11 15 52

If @cameronoelsen or anyone else that like to do design things want to do something... that would be nice :-)

Icon for Jupyter / notebook / qtconsole

Silly Windows question, apologies in advance. Do you have a preferred icon for Jupyter / notebook / qtconsole shortcuts created by Anaconda? I have looked for .ico files in several repositories, but see none.

Ambiguous instructions for installing python2 and python3 kernels, Big Split path issues?

In attempting to collaborate with @suchow, we ran into an issue with his jupyter notebook having been installed through python2 and my having written the notebook with a python3 kernel in mind.

He had an ipython3 version of the notebook with python3 as its kernel, but that would not run Python 3.5.

In trying to figure out how to fix the original problem (i.e., a jupyter notebook installed through python2 not having access to a python3 kernel) I began a long trek through a lot of conflicting documentation, this issue is the trail as I tried to recreate it (I am guessing I left out some parts).

I ended up at this documentation which only says that a Python kernel is installed when you installed the notebook https://github.com/jupyter/jupyter/blob/master/docs/source/install.rst.

Look at http://jupyter.cs.brynmawr.edu/hub/dblank/public/Jupyter%20Help.ipynb#1.4.2-Enable-Python-3-kernel but that seems to use the ~/.ipython/kernels/ path rather than the post Big Split path which seems to be ~/Library/Jupyter or /usr/local/share/jupyter (since ~/.jupyter is for config files, not data files and kernels are data files).

Eventually I found http://jupyter.readthedocs.org/en/latest/migrating.html#kernels, which says

You can see where the file is with jupyter kernelspec list, and then modify kernels/python3/kernel.json by hand. a2km is an experimental project that tries to make these things easier.

But the file path is not returned when I run jupyter kernelspec list, all it does is return

Available kernels:
  python3

And going from to https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages includes no instructions for how to install a Python 2 kernel if you began with a Python 3 kernel (or vice-versa).

I only noticed now that

IPython.kerneljupyter_client, ipykernel (IPython.kernel became two packages - one for the client-side APIs, one for the IPython kernel for Jupyter)

which leads me to look at http://ipython.org/ipython-doc/dev/development/kernels.html

Which suggests (contrary to the above jupyter migration documentation)

To see the available kernel specs, run:

   ipython kernelspec list

(which also only returns a list of the kernels with no path)

And also says:

  Unix Windows
System

/usr/share/jupyter/kernels

/usr/local/share/jupyter/kernels

%PROGRAMDATA%\jupyter\kernels
User ~/.ipython/kernels

which conflicts with the above claim that it should be in either /usr/local/share/jupyter/kernels or ~/Library/Jupyter (if local) on OSX Unix systems, and suggests continued use of the ~/.ipython/kernels path (which I should mention, does not exist on my machine).

I'm genuinely baffled as to how to either instruct someone else to install a python3 kernel on their machine or to install a python2 kernel on mine…

Just to check these are the errors I got when I tried to run

jupyter kernelspec install python2
Traceback (most recent call last):
  File "/usr/local/bin/jupyter-kernelspec", line 8, in <module>
    main()
  File "/usr/local/bin/jupyter-kernelspec", line 5, in main
    KernelSpecApp.launch_instance()
  File "/usr/local/lib/python3.4/site-packages/traitlets/config/application.py", line 592, in launch_instance
    app.start()
  File "/usr/local/lib/python3.4/site-packages/jupyter_client/kernelspecapp.py", line 177, in start
    return self.subapp.start()
  File "/usr/local/lib/python3.4/site-packages/jupyter_client/kernelspecapp.py", line 113, in start
    replace=self.replace,
  File "/usr/local/lib/python3.4/site-packages/jupyter_client/kernelspec.py", line 208, in install_kernel_spec
    shutil.copytree(source_dir, destination)
  File "/usr/local/Cellar/python3/3.4.1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/shutil.py", line 296, in copytree
    names = os.listdir(src)
FileNotFoundError: [Errno 2] No such file or directory: 'python2'

Which returned similar errors when run with python2.7,python27,PYTHON2,PYTHON2.7,PYTHON27 and even python.

Regardless, the amount of hoops I had to go through and the number of conflicts I ran into suggested to me that this needs more documentation on how to do.

I'm happy to help write the necessary changes in all the places I found (plus a number of stackexchange answers that I think may be inconsistent with the Big Split… I've posted links to at the bottom of this Issue), I just need to know how to solve the problem at least on my system before I can help with fixing the inconsistent documentation.

No matter what, it would seem to make sense to point out that there are two potential python kernels that the jupyter notebook can use, and I would argue that installation instructions for running both side-by-side should be included in the core documentation (or at least in the list of available kernels page).

relevant Stack-overflow answers with ambiguous relevance due to big split:

http://stackoverflow.com/questions/30492623/using-both-python-2-x-and-python-3-x-in-ipython-notebook
especially the answer: http://stackoverflow.com/a/30493155/1816995
http://stackoverflow.com/questions/32258277/how-can-i-run-python-2-7-3-4-notebooks-side-by-side-in-jupyter-ipython
http://stackoverflow.com/questions/29773954/change-ipython-3-for-python-3-kernel-to-python2-for-the-cluster-too
http://stackoverflow.com/questions/28831854/how-do-i-add-python3-kernel-to-jupyter-ipython

Error in Jupyter installation

Hello, I currently have Python 2.7.10 on my system. I am running Mac OSX 10.11.1. I successfully installed Anaconda and Jupyter. However, when I run Jupyter, I get the error below. Could someone please help? I'd really like to use Jupyter.

Traceback (most recent call last):
  File "/Users/jlu96/anaconda/bin/jupyter-notebook", line 4, in <module>
    import notebook.notebookapp
  File "/Users/jlu96/anaconda/lib/python3.5/site-packages/notebook/__init__.py", line 25, in <module>
    from .nbextensions import install_nbextension
  File "/Users/jlu96/anaconda/lib/python3.5/site-packages/notebook/nbextensions.py", line 227, in <module>
    from jupyter_core.application import JupyterApp
  File "/Users/jlu96/anaconda/lib/python3.5/site-packages/jupyter_core/application.py", line 30, in <module>
    from traitlets.config.application import Application, catch_config_error
  File "/Users/jlu96/anaconda/lib/python3.5/site-packages/traitlets/config/__init__.py", line 6, in <module>
    from .application import *
  File "/Users/jlu96/anaconda/lib/python3.5/site-packages/traitlets/config/application.py", line 17, in <module>
    from decorator import decorator
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/decorator.py", line 273, in <module>
    contextmanager = decorator(ContextManager)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/decorator.py", line 234, in decorator
    evaldict = callerfunc.func_globals.copy()
AttributeError: 'function' object has no attribute 'func_globals'

Strange display of Jupyter

I'm new to Jupyter notebook, but the jupyter display looks different than the regular one.

image

Anyone knows about the issue? and how to resolve it?

can not launch jupyter on window x64

Python 3.5 is on windows 64.
Use command
pip3 install jupyter
to deploy jupyter packages.

Installation completed successfully.
But after that all attepts to launch it with command jupyter notebook fail with error message:there is no MSVCP140.dll

Tried to install VS2013 C++ redistributable package. That did not change anything.

[idea] jupyter <subcommand> --docs

Would open the web browser for the docs of the target subcommand, potentially the right version as it has access to the version number.

Thoughts ?

Line Numbers are not saved

Jupyter doesn't seem to save the line numbers.

I like the toggle line numbers feature in code cells or raw NBconvert cells, because they enhance the readability of these cells. However, when the notebook is saved, closed and re-opened, the line numbers disappear. Is this a bug?

Running this on:
Mac OSX 10.10.4
Python 2.7.10-0
IPython 3.2.0

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.