| Name | jupytext JSON |
| Version |
1.16.6
JSON |
| download |
| home_page | None |
| Summary | Jupyter notebooks as Markdown documents, Julia, Python or R scripts |
| upload_time | 2024-12-17 19:43:26 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.8 |
| license | MIT License Copyright (c) 2018-2023 Marc Wouts Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. |
| keywords |
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
<!-- INDEX-START -->
[](https://github.com/mwouts/jupytext/actions)
[](https://jupytext.readthedocs.io/en/latest/?badge=latest)
[](https://codecov.io/gh/mwouts/jupytext/branch/main)
[](LICENSE)
[](https://github.com/psf/black)
[](docs/languages.md)
[](https://anaconda.org/conda-forge/jupytext)
[](https://pypi.python.org/pypi/jupytext)
[](https://pypi.python.org/pypi/jupytext)
[](https://mybinder.org/v2/gh/mwouts/jupytext/main?urlpath=lab/tree/demo/get_started.ipynb)
[](https://mybinder.org/v2/gh/mwouts/jupytext/main?filepath=demo)
[](https://renkulab.io/projects/best-practices/jupytext/sessions/new?autostart=1)
[](https://www.youtube.com/watch?v=SDYdeVfMh48)
# Jupytext
Have you always wished Jupyter notebooks were plain text documents? Wished you could edit them in your favorite IDE? And get clear and meaningful diffs when doing version control? Then, Jupytext may well be the tool you're looking for!
## Text Notebooks
A Python notebook encoded in the `py:percent` [format](docs/formats-scripts.md#the-percent-format) has a `.py` extension and looks like this:
```
# %% [markdown]
# This is a markdown cell
# %%
def f(x):
return 3*x+1
```
Only the notebook inputs (and optionally, the metadata) are included. Text notebooks are well suited for version control. You can also edit or refactor them in an IDE - the `.py` notebook above is a regular Python file.
We recommend the `percent` format for notebooks that mostly contain code. The `percent` format is available for Julia, Python, R and many other [languages](docs/languages.md).
If your notebook is documentation-oriented, a [Markdown-based format](docs/formats-markdown.md) (text notebooks with a `.md` extension) might be more appropriate. Depending on what you plan to do with your notebook, you might prefer the Myst Markdown format, which interoperates very well with Jupyter Book, or Quarto Markdown, or even Pandoc Markdown.
## Installation
Install Jupytext in the Python environment that you use for Jupyter. Use either
pip install jupytext
or
conda install jupytext -c conda-forge
Then, restart your Jupyter Lab server, and make sure Jupytext is activated in Jupyter: `.py` and `.md` files have a Notebook icon, and you can open them as Notebooks with a right click in Jupyter Lab.
## Paired Notebooks
Text notebooks with a `.py` or `.md` extension are well suited for version control. They can be edited or authored conveniently in an IDE. You can open and run them as notebooks in Jupyter Lab with a right click. However, the notebook outputs are lost when the notebook is closed, as only the notebook inputs are saved in text notebooks.
A convenient alternative to text notebooks are [paired notebooks](docs/paired-notebooks.md). These are a set of two files, say `.ipynb` and `.py`, that contain the same notebook, but in different formats.
You can edit the `.py` version of the paired notebook, and get the edits back in Jupyter by selecting _reload notebook from disk_. The outputs will be reloaded from the `.ipynb` file, if it exists. The `.ipynb` version will be updated or recreated the next time you save the notebook in Jupyter.
To pair a notebook in Jupyter Lab, use the command `Pair Notebook with percent Script` from the Command Palette:
To pair all the notebooks in a certain directory, create a [configuration file](docs/config.md) with this content:
```
# jupytext.toml at the root of your notebook directory
formats = "ipynb,py:percent"
```
## Command line
Jupytext is also available at the [command line](docs/using-cli.md). You can
- pair a notebook with `jupytext --set-formats ipynb,py:percent notebook.ipynb`
- synchronize the paired files with `jupytext --sync notebook.py` (the inputs are loaded from the most recent paired file)
- convert a notebook in one format to another with `jupytext --to ipynb notebook.py` (use `-o` if you want a specific output file)
- pipe a notebook to a linter with e.g. `jupytext --pipe black notebook.ipynb`
## Sample use cases
### Notebooks under version control
This is a quick how-to:
- Open your `.ipynb` notebook in Jupyter and [pair](docs/paired-notebooks.md) it to a `.py` notebook, using either the _pair_ command in Jupyter Lab, or a global [configuration file](docs/config.md)
- Save the notebook - this creates a `.py` notebook
- Add this `.py` notebook to version control
You might exclude `.ipynb` files from version control (unless you want to see the outputs versioned!). Jupytext will recreate the `.ipynb` files locally when the users open and save the `.py` notebooks.
### Collaborating on notebooks with Git
Collaborating on Jupyter notebooks through Git becomes as easy as collaborating on text files.
Assume that you have your `.py` notebooks under version control (see above). Then,
- Your collaborator pulls the `.py` notebook
- They open it _as a notebook_ in Jupyter (right-click in Jupyter Lab)
- At that stage the notebook has no outputs. They run the notebook and save it. Outputs are regenerated, and a local `.ipynb` file is created
- They edit the notebook, and push the updated `notebook.py` file. The diff is nothing else than a standard diff on a Python script.
- You pull the updated `notebook.py` script, and refresh your browser. The input cells are updated based on the new content of `notebook.py`. The outputs are reloaded from your local `.ipynb` file. Finally, the kernel variables are untouched, so you have the option to run only the modified cells to get the new outputs.
### Editing or refactoring a notebook in an IDE
Once your notebook is [paired](docs/paired-notebooks.md) with a `.py` file, you can easily edit or refactor the `.py` representation of the notebook in an IDE.
Once you are done editing the `.py` notebook, you will just have to _reload_ the notebook in Jupyter to get the latest edits there.
Note: It is simpler to close the `.ipynb` notebook in Jupyter when you edit the paired `.py` file. There is no obligation to do so; however, if you don't, you should be prepared to read carefully the pop-up messages. If Jupyter tries to save the notebook while the paired `.py` file has also been edited on disk since the last reload, a conflict will be detected and you will be asked to decide which version of the notebook (in memory or on disk) is the appropriate one.
## More resources
Read more about Jupytext in the [documentation](https://jupytext.readthedocs.io).
If you're new to Jupytext, you may want to start with the [FAQ](docs/faq.md) or with the [Tutorials](docs/tutorials.md).
There is also this short introduction to Jupytext: [](https://www.youtube.com/watch?v=SDYdeVfMh48).
Raw data
{
"_id": null,
"home_page": null,
"name": "jupytext",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": null,
"author": null,
"author_email": "Marc Wouts <marc.wouts@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/10/e7/58d6fd374e1065d2bccefd07953d2f1f911d8de03fd7dc33dd5a25ac659c/jupytext-1.16.6.tar.gz",
"platform": null,
"description": "\n\n<!-- INDEX-START -->\n\n[](https://github.com/mwouts/jupytext/actions)\n[](https://jupytext.readthedocs.io/en/latest/?badge=latest)\n[](https://codecov.io/gh/mwouts/jupytext/branch/main)\n[](LICENSE)\n[](https://github.com/psf/black)\n[](docs/languages.md)\n[](https://anaconda.org/conda-forge/jupytext)\n[](https://pypi.python.org/pypi/jupytext)\n[](https://pypi.python.org/pypi/jupytext)\n[](https://mybinder.org/v2/gh/mwouts/jupytext/main?urlpath=lab/tree/demo/get_started.ipynb)\n[](https://mybinder.org/v2/gh/mwouts/jupytext/main?filepath=demo)\n[](https://renkulab.io/projects/best-practices/jupytext/sessions/new?autostart=1)\n[](https://www.youtube.com/watch?v=SDYdeVfMh48)\n\n# Jupytext\n\nHave you always wished Jupyter notebooks were plain text documents? Wished you could edit them in your favorite IDE? And get clear and meaningful diffs when doing version control? Then, Jupytext may well be the tool you're looking for!\n\n## Text Notebooks\n\nA Python notebook encoded in the `py:percent` [format](docs/formats-scripts.md#the-percent-format) has a `.py` extension and looks like this:\n\n```\n# %% [markdown]\n# This is a markdown cell\n\n# %%\ndef f(x):\n return 3*x+1\n```\n\nOnly the notebook inputs (and optionally, the metadata) are included. Text notebooks are well suited for version control. You can also edit or refactor them in an IDE - the `.py` notebook above is a regular Python file.\n\nWe recommend the `percent` format for notebooks that mostly contain code. The `percent` format is available for Julia, Python, R and many other [languages](docs/languages.md).\n\nIf your notebook is documentation-oriented, a [Markdown-based format](docs/formats-markdown.md) (text notebooks with a `.md` extension) might be more appropriate. Depending on what you plan to do with your notebook, you might prefer the Myst Markdown format, which interoperates very well with Jupyter Book, or Quarto Markdown, or even Pandoc Markdown.\n\n## Installation\n\nInstall Jupytext in the Python environment that you use for Jupyter. Use either\n\n pip install jupytext\n\nor\n\n conda install jupytext -c conda-forge\n\nThen, restart your Jupyter Lab server, and make sure Jupytext is activated in Jupyter: `.py` and `.md` files have a Notebook icon, and you can open them as Notebooks with a right click in Jupyter Lab.\n\n\n\n## Paired Notebooks\n\nText notebooks with a `.py` or `.md` extension are well suited for version control. They can be edited or authored conveniently in an IDE. You can open and run them as notebooks in Jupyter Lab with a right click. However, the notebook outputs are lost when the notebook is closed, as only the notebook inputs are saved in text notebooks.\n\nA convenient alternative to text notebooks are [paired notebooks](docs/paired-notebooks.md). These are a set of two files, say `.ipynb` and `.py`, that contain the same notebook, but in different formats.\n\nYou can edit the `.py` version of the paired notebook, and get the edits back in Jupyter by selecting _reload notebook from disk_. The outputs will be reloaded from the `.ipynb` file, if it exists. The `.ipynb` version will be updated or recreated the next time you save the notebook in Jupyter.\n\nTo pair a notebook in Jupyter Lab, use the command `Pair Notebook with percent Script` from the Command Palette:\n\n\n\nTo pair all the notebooks in a certain directory, create a [configuration file](docs/config.md) with this content:\n\n```\n# jupytext.toml at the root of your notebook directory\nformats = \"ipynb,py:percent\"\n```\n\n## Command line\n\nJupytext is also available at the [command line](docs/using-cli.md). You can\n\n- pair a notebook with `jupytext --set-formats ipynb,py:percent notebook.ipynb`\n- synchronize the paired files with `jupytext --sync notebook.py` (the inputs are loaded from the most recent paired file)\n- convert a notebook in one format to another with `jupytext --to ipynb notebook.py` (use `-o` if you want a specific output file)\n- pipe a notebook to a linter with e.g. `jupytext --pipe black notebook.ipynb`\n\n## Sample use cases\n\n### Notebooks under version control\n\nThis is a quick how-to:\n- Open your `.ipynb` notebook in Jupyter and [pair](docs/paired-notebooks.md) it to a `.py` notebook, using either the _pair_ command in Jupyter Lab, or a global [configuration file](docs/config.md)\n- Save the notebook - this creates a `.py` notebook\n- Add this `.py` notebook to version control\n\nYou might exclude `.ipynb` files from version control (unless you want to see the outputs versioned!). Jupytext will recreate the `.ipynb` files locally when the users open and save the `.py` notebooks.\n\n### Collaborating on notebooks with Git\n\nCollaborating on Jupyter notebooks through Git becomes as easy as collaborating on text files.\n\nAssume that you have your `.py` notebooks under version control (see above). Then,\n- Your collaborator pulls the `.py` notebook\n- They open it _as a notebook_ in Jupyter (right-click in Jupyter Lab)\n- At that stage the notebook has no outputs. They run the notebook and save it. Outputs are regenerated, and a local `.ipynb` file is created\n- They edit the notebook, and push the updated `notebook.py` file. The diff is nothing else than a standard diff on a Python script.\n- You pull the updated `notebook.py` script, and refresh your browser. The input cells are updated based on the new content of `notebook.py`. The outputs are reloaded from your local `.ipynb` file. Finally, the kernel variables are untouched, so you have the option to run only the modified cells to get the new outputs.\n\n### Editing or refactoring a notebook in an IDE\n\nOnce your notebook is [paired](docs/paired-notebooks.md) with a `.py` file, you can easily edit or refactor the `.py` representation of the notebook in an IDE.\n\nOnce you are done editing the `.py` notebook, you will just have to _reload_ the notebook in Jupyter to get the latest edits there.\n\nNote: It is simpler to close the `.ipynb` notebook in Jupyter when you edit the paired `.py` file. There is no obligation to do so; however, if you don't, you should be prepared to read carefully the pop-up messages. If Jupyter tries to save the notebook while the paired `.py` file has also been edited on disk since the last reload, a conflict will be detected and you will be asked to decide which version of the notebook (in memory or on disk) is the appropriate one.\n\n## More resources\n\nRead more about Jupytext in the [documentation](https://jupytext.readthedocs.io).\n\nIf you're new to Jupytext, you may want to start with the [FAQ](docs/faq.md) or with the [Tutorials](docs/tutorials.md).\n\nThere is also this short introduction to Jupytext: [](https://www.youtube.com/watch?v=SDYdeVfMh48).\n",
"bugtrack_url": null,
"license": "MIT License Copyright (c) 2018-2023 Marc Wouts Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.",
"summary": "Jupyter notebooks as Markdown documents, Julia, Python or R scripts",
"version": "1.16.6",
"project_urls": {
"Documentation": "https://jupytext.readthedocs.io",
"Homepage": "https://github.com/mwouts/jupytext",
"Source Code": "https://github.com/mwouts/jupytext"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "f40227191f18564d4f2c0e543643aa94b54567de58f359cd6a3bed33adb723ac",
"md5": "1def2bca3cc793240c39e32360b85f16",
"sha256": "900132031f73fee15a1c9ebd862e05eb5f51e1ad6ab3a2c6fdd97ce2f9c913b4"
},
"downloads": -1,
"filename": "jupytext-1.16.6-py3-none-any.whl",
"has_sig": false,
"md5_digest": "1def2bca3cc793240c39e32360b85f16",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 154200,
"upload_time": "2024-12-17T19:43:24",
"upload_time_iso_8601": "2024-12-17T19:43:24.882981Z",
"url": "https://files.pythonhosted.org/packages/f4/02/27191f18564d4f2c0e543643aa94b54567de58f359cd6a3bed33adb723ac/jupytext-1.16.6-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "10e758d6fd374e1065d2bccefd07953d2f1f911d8de03fd7dc33dd5a25ac659c",
"md5": "21e1b116760109b2f53ffc503b75621d",
"sha256": "dbd03f9263c34b737003f388fc069e9030834fb7136879c4c32c32473557baa0"
},
"downloads": -1,
"filename": "jupytext-1.16.6.tar.gz",
"has_sig": false,
"md5_digest": "21e1b116760109b2f53ffc503b75621d",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 3726029,
"upload_time": "2024-12-17T19:43:26",
"upload_time_iso_8601": "2024-12-17T19:43:26.862494Z",
"url": "https://files.pythonhosted.org/packages/10/e7/58d6fd374e1065d2bccefd07953d2f1f911d8de03fd7dc33dd5a25ac659c/jupytext-1.16.6.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-12-17 19:43:26",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "mwouts",
"github_project": "jupytext",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "jupytext"
}
