naucse
This is a server for open course material.
To use it, you will need some content.
Usually, the repository with the content will require the naucse module,
and will run using python -m naucse.
We use content at https://github.com/pyvec/naucse.python.cz to generate naucse.python.cz.
Installation
Install from a virtual environment.
To install the latest release:
(venv)$ python -m pip install naucse
To install from a cloned repository, for development:
(venv)$ python -m pip install -e.[dev]
Running
To run the serve, either change (cd) to the directory with content,
or set NAUCSE_ROOT_PATH to that directory.
Then run:
(venv)$ python -m naucse serve
Instead of serve, you can run freeze to generate a static website.
See Elsa for other usage, including
deployment to GitHub Pages.
Served courses
The courses on the served website are taken from two sources:
-
courses.ymlin$NAUCSE_ROOT_PATH, with entries like:course_slug: url: https://github.com/user/repo branch: main path: _compiled
The named repositories will be cloned. At the given path in the given branch, naucse expects compiled course info, as prepared by
python -m naucse_render compile.This is intended for the production site, which aggregates lots of individual courses.
If
courses.ymlis present, naucse will use a pretty homepage (rather than listing all courses on the homepage). -
Any courses found by
python -m naucse_render ls. This is useful when developing a course locally.
Tests
Tests can be run using tox:
(venv)$ tox
or pytest directly:
(venv)$ python -m pytest
Licence
The code is licensed under the terms of the MIT license, see LICENSE.MIT file for full text. By contributing code to this repository, you agree to have it licensed under the same license.
Content has its own license specified in the appropriate matadata. Only free content licenses are used. By contributing to an already licensed document, you agree to have it licensed under the same license. (And feel free to add yourself to the authors list in its metadata.) When contributing new document(s) a license must be specified in the metadata.
Metadata
Release files for naucse 0.5.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| naucse-0.5.3.tar.gz | 813.6 kB | Without provenance | Details for naucse-0.5.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| naucse-0.5.3-py3-none-any.whl | Python 3 | none | any | Details for naucse-0.5.3-py3-none-any.whl |
Total release size: 1.6 MB
Release files / naucse-0.5.3.tar.gz
| Download URL | naucse-0.5.3.tar.gz |
|---|---|
| Size | 813.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b6b3d3a06680eb8cb8319fe8ab29e1709c132293c4da9989ffa88527843f0a85
|
|
BLAKE2b-256 checksum How to use checksums |
6c7c1ee27fab59b9a58d71a742459174878dd1641e2554c8d904d3362f92146f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 CPython/3.10.9
|
Release files / naucse-0.5.3-py3-none-any.whl
| Download URL | naucse-0.5.3-py3-none-any.whl |
|---|---|
| Size | 785.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5a791f99ef21e01734bece7de134bd185dad907629df956caeb9c44d669b7454
|
|
BLAKE2b-256 checksum How to use checksums |
ef193c6096f05fc0e30334185ea176e6721ab39767f2ca69394570e418ebfb22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 CPython/3.10.9
|
Security for naucse 0.5.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.