pipnest
pipnest packages your NEST extension modules into pip installable packages. This is a benefit when you're distributing a Python model for the NEST simulator and have a dependency on an extension module. Instead of having to provide installation instructions to your end-users you can have pip download and build the extension module into the target machine's nest installation.
Usage
Project structure
- Prepare a folder with 1 subfolder that contains a NEST extension modules.
- The source code of the extension module can not be in the root repository.
- The name of your module should be the name of your folders plus "module".
Your project structure should look like this:
- my_module
- my_module
- my_file1.cpp
- my_file2.cpp
- ...
In this example your NEST module should be called the my_modulemodule.
Initialize project
Run the pipnest init command from the root folder and fill in the
requested metadata:
cd my_module
pipnest init .
This should create a setup.py and README.md, be sure to edit the latter.
Check that your module is present under the packages keyword argument
in setup.py.
Package
Create the source distribution:
python setup.py sdist
Test your package locally
- Remove any already installed versions from the
$NEST_INSTALL_DIR/lib/nestfolder - Run
pip install dist/*. (If an MPI error occurs, restart your terminal and try again)
Upload to PyPI
Use twine to upload your package:
twine upload dist/* --skip-existing
Metadata
Release files for pipnest 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pipnest-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for pipnest-0.0.2-py3-none-any.whl |
Release files / pipnest-0.0.2-py3-none-any.whl
| Download URL | pipnest-0.0.2-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
834479696dd5120a9056a1e52aab861ea7ddf6b032120e9c28141bf871c9788f
|
|
BLAKE2b-256 checksum How to use checksums |
c7358c85e8b7779009c6581adb905c36886eaed5795dda24d01ac63f7c49a631
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/42.0.2 requests-toolbelt/0.9.1 tqdm/4.38.0 CPython/3.6.9
|
Security for pipnest 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.