You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+33-3Lines changed: 33 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,6 @@ Core common functionality of Jupyter projects.
5
5
This package contains base application classes and configuration inherited by other projects.
6
6
It doesn't do much on its own.
7
7
8
-
9
8
# Development Setup
10
9
11
10
The [Jupyter Contributor Guides](http://jupyter.readthedocs.io/en/latest/contributor/content-contributor.html) provide extensive information on contributing code or documentation to Jupyter projects. The limited instructions below for setting up a development environment are for your convenience.
@@ -23,6 +22,38 @@ and download the dependencies of code and test suite by executing:
23
22
24
23
The last command runs the test suite to verify the setup. During development, you can pass filenames to `py.test`, and it will execute only those tests.
25
24
25
+
## Code Styling
26
+
27
+
`jupyter_core` has adopted automatic code formatting so you shouldn't
28
+
need to worry too much about your code style.
29
+
As long as your code is valid,
30
+
the pre-commit hook should take care of how it should look.
31
+
`pre-commit` and its associated hooks will automatically be installed when
32
+
you run `pip install -e ".[test]"`
33
+
34
+
To install `pre-commit` manually, run the following:
35
+
36
+
```bash
37
+
pip install pre-commit
38
+
pre-commit install
39
+
```
40
+
41
+
You can invoke the pre-commit hook by hand at any time with:
42
+
43
+
```bash
44
+
pre-commit run
45
+
```
46
+
47
+
which should run any autoformatting on your code
48
+
and tell you about any errors it couldn't fix automatically.
49
+
You may also install [black integration](https://github.com/psf/black#editor-integration)
50
+
into your text editor to format code automatically.
51
+
52
+
If you have already committed files before setting up the pre-commit
53
+
hook with `pre-commit install`, you can fix everything up using
54
+
`pre-commit run --all-files`. You need to make the fixing commit
55
+
yourself after that.
56
+
26
57
## Documentation
27
58
28
59
The documentation of Jupyter Core is generated from the files in `docs/` using Sphinx. Instructions for setting up Sphinx with a selection of optional modules are in the [Documentation Guide](http://jupyter.readthedocs.io/en/latest/contrib_docs/index.html). You'll also need the `make` command.
@@ -37,5 +68,4 @@ The following commands build the documentation in HTML format and check for brok
37
68
38
69
Point your browser to the following URL to access the generated documentation:
milestone on GitHub for the full list of pull requests and issues closed.
35
35
36
-
- Add Python site user base subdirectories to config and data user-level paths if ``site.ENABLE_USER_SITE`` is True. One way to disable these directory additions is to set the ``PYTHONNOUSERSITE`` environment variable. These locations can be customized by setting the ``PYTHONUSERBASE`` environment variable. (:ghpull:`242`)
36
+
- Add Python site user base subdirectories to config and data user-level paths
37
+
if ``site.ENABLE_USER_SITE`` is True. One way to disable these directory
38
+
additions is to set the ``PYTHONNOUSERSITE`` environment variable. These
39
+
locations can be customized by setting the ``PYTHONUSERBASE`` environment
40
+
variable. (:ghpull:`242`)
37
41
38
42
39
43
4.8
@@ -44,7 +48,10 @@ milestone on GitHub for the full list of pull requests and issues closed.
jupyter_core 4.8.1 was released the same day as 4.8.0 and also included the fix below for the Windows tests. Unfortunately, the 4.8.1 release commit and tag were not pushed to GitHub. We are releasing 4.8.2 so we have a commit and tag in version control.
51
+
jupyter_core 4.8.1 was released the same day as 4.8.0 and also included the fix
52
+
below for the Windows tests. Unfortunately, the 4.8.1 release commit and tag
53
+
were not pushed to GitHub. We are releasing 4.8.2 so we have a commit and tag
milestone on GitHub for the full list of pull requests and issues closed.
91
98
92
-
- Add a new ``JUPYTER_PREFER_ENV_PATH`` variable, which can be set to switch the order of the environment-level path and the user-level path in the Jupyter path hierarchy (e.g., ``jupyter --paths``). It is considered set if it is a value that is not one of 'no', 'n', 'off', 'false', '0', or '0.0' (case insensitive). If you are running Jupyter in multiple virtual environments as the same user, you will likely want to set this environment variable.
99
+
- Add a new ``JUPYTER_PREFER_ENV_PATH`` variable, which can be set to switch
100
+
the order of the environment-level path and the user-level path in the
101
+
Jupyter path hierarchy (e.g., ``jupyter --paths``). It is considered set if
102
+
it is a value that is not one of 'no', 'n', 'off', 'false', '0', or '0.0'
103
+
(case insensitive). If you are running Jupyter in multiple virtual
104
+
environments as the same user, you will likely want to set this environment
105
+
variable.
93
106
- Drop Python 2.x and 3.5 support, as they have reached end of life.
94
107
- Add Python 3.9 builds to testing, and expand testing to cover Windows, macOS, and Linux platforms.
95
108
- ``jupyter --paths --debug`` now explains the environment variables that affect the current path list.
0 commit comments