cWeb
The client for web renders web pages and transforms them into whatever format you need.
CLI Installation
pip install cWeb
cWeb https://sanchezcarlosjr.notion.site/Learn-to-make-cool-ideas-here-d80df9eb663f440aa8076c6422c54a93?pvs=4
Full Installation
In order to set up the necessary environment:
- review and uncomment what you need in
environment.ymland create an environmentcWebwith the help of conda:conda env create -f environment.yml - activate the new environment with:
conda activate cWeb
NOTE: The conda environment will have cWeb installed in editable mode. Some changes, e.g. in
setup.cfg, might require you to runpip install -e .again.
Optional and needed only once after git clone:
-
install several pre-commit git hooks with:
pre-commit install # You might also want to run `pre-commit autoupdate`
and checkout the configuration under
.pre-commit-config.yaml. The-n, --no-verifyflag ofgit commitcan be used to deactivate pre-commit hooks temporarily. -
install nbstripout git hooks to remove the output cells of committed notebooks with:
nbstripout --install --attributes notebooks/.gitattributes
This is useful to avoid large diffs due to plots in your notebooks. A simple
nbstripout --uninstallwill revert these changes.
Then take a look into the scripts and notebooks folders.
Dependency Management & Reproducibility
- Always keep your abstract (unpinned) dependencies updated in
environment.ymland eventually insetup.cfgif you want to ship and install your package viapiplater on. - Create concrete dependencies as
environment.lock.ymlfor the exact reproduction of your environment with:conda env export -n cWeb -f environment.lock.yml
For multi-OS development, consider using--no-buildsduring the export. - Update your current environment with respect to a new
environment.lock.ymlusing:conda env update -f environment.lock.yml --prune
Project Organization
├── AUTHORS.md <- List of developers and maintainers.
├── CHANGELOG.md <- Changelog to keep track of new features and fixes.
├── CONTRIBUTING.md <- Guidelines for contributing to this project.
├── Dockerfile <- Build a docker container with `docker build .`.
├── LICENSE.txt <- License as chosen on the command-line.
├── README.md <- The top-level README for developers.
├── configs <- Directory for configurations of model & application.
├── data
│ ├── external <- Data from third party sources.
│ ├── interim <- Intermediate data that has been transformed.
│ ├── processed <- The final, canonical data sets for modeling.
│ └── raw <- The original, immutable data dump.
├── docs <- Directory for Sphinx documentation in rst or md.
├── environment.yml <- The conda environment file for reproducibility.
├── models <- Trained and serialized models, model predictions,
│ or model summaries.
├── notebooks <- Jupyter notebooks. Naming convention is a number (for
│ ordering), the creator's initials and a description,
│ e.g. `1.0-fw-initial-data-exploration`.
├── pyproject.toml <- Build configuration. Don't change! Use `pip install -e .`
│ to install for development or to build `tox -e build`.
├── references <- Data dictionaries, manuals, and all other materials.
├── reports <- Generated analysis as HTML, PDF, LaTeX, etc.
│ └── figures <- Generated plots and figures for reports.
├── scripts <- Analysis and production scripts which import the
│ actual PYTHON_PKG, e.g. train_model.
├── setup.cfg <- Declarative configuration of your project.
├── setup.py <- [DEPRECATED] Use `python setup.py develop` to install for
│ development or `python setup.py bdist_wheel` to build.
├── src
│ └── cweb <- Actual Python package where the main functionality goes.
├── tests <- Unit tests which can be run with `pytest`.
├── .coveragerc <- Configuration for coverage reports of unit tests.
├── .isort.cfg <- Configuration for git hook that sorts imports.
└── .pre-commit-config.yaml <- Configuration of pre-commit git hooks.
Note
This project has been set up using PyScaffold 4.5 and the dsproject extension 0.0.post158+g5fb5c40.d20231203.
Metadata
Release files for cWeb 1.0.0
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 |
|---|---|---|---|---|
| cWeb-1.0.0.tar.gz | 27.0 kB | Without provenance | Details for cWeb-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cWeb-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for cWeb-1.0.0-py3-none-any.whl |
Total release size: 33.9 kB
Release files / cWeb-1.0.0.tar.gz
| Download URL | cWeb-1.0.0.tar.gz |
|---|---|
| Size | 27.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
299126a54915bb60981f2c9b17b70cb506e030b8559f48c1ba1e5d5a782f629a
|
|
BLAKE2b-256 checksum How to use checksums |
253a840b02295ddf83b2bbea1353d13d03babe4f525be29896197f291ee2e994
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Release files / cWeb-1.0.0-py3-none-any.whl
| Download URL | cWeb-1.0.0-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
30905a735cd3c2d647a30ae437f1b7152083e2f600729f24b12c45aa9186f5dc
|
|
BLAKE2b-256 checksum How to use checksums |
b35f49f34059338500fc5ae1d88185ec4a39deeddd903fc51ae37e315d0c2c31
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Security for cWeb 1.0.0
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.