Nosem build system
Nosem is tiny overlay to Meson.
While you call meson to interpret you meson.build file, with nosem you directly invoke your build.py.
This inverted process removes many limitations from meson and you are free to use any python library directly.
The whole scripting part of meson is bypassed
Meson
meson.build:
project('myproj', 'cpp')
executable('example', 'main.cpp')
meson build
cd build && ninja
Nosem
nosem.build.py:
from nosem import project, executable
project('myproj', 'cpp')
executable('example', 'main.cpp')
nosem build
cd build && ninja
API
The API is exactly the same as meson available here. It defers only in the syntax, nosem.build.py files are pure python.
How it works
The meson.build script interpretation is bypassed, simply replaced by a python module loading.
Metadata
Release files for nosem 0.0.2
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 | |
|---|---|---|---|---|
| nosem-0.0.2.tar.gz | 5.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nosem-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.6 kB
Release files / nosem-0.0.2.tar.gz
| Download URL | nosem-0.0.2.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0c8b6271292df245f55dcadf390e7e26a206c2194815ba92e8674149107bed2b
|
|
BLAKE2b-256 checksum How to use checksums |
f2fd4a2e480cd4aa43ded3d6705974f7b2939ed25292bc9dc0e20e1d695f297b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.9.5
|
Release files / nosem-0.0.2-py3-none-any.whl
| Download URL | nosem-0.0.2-py3-none-any.whl |
|---|---|
| Size | 7.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6de15cf377d8e16cf918fa751c9421945936fcede565a2ecbd2580c915a8531f
|
|
BLAKE2b-256 checksum How to use checksums |
2abeeeff651564152dac39d9752c604adb2d77ec80557b0f16b953f57470a3f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.9.5
|
Security for nosem 0.0.2
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.