dirac-webapp-packaging
Build tools for compiling javascript sources in DIRAC WebApp packages.
Usage
These instructions assume you are using a setup.cfg file to use setuptools to build your package with versioning being handled by setuptools-scm.
In order to use this to automatically compile javascript sources as part of wheel generation the pyproject.toml:
[build-system]
requires = ["dirac_webapp_packaging~=1.0", "WebAppDIRAC ~=4.3.0a0", "setuptools_scm[toml]>=3.4"]
build-backend = "setuptools.build_meta"
[tool.setuptools_scm]
# Avoid letting setuptools_scm use old style tags (i.e. vXrYpZ)
git_describe_command = "git describe --dirty --tags --long --match *[0-9]* --exclude v[0-9]r* --exclude v[0-9][0-9]r*"
and, assuming your other metadata is in a setup.cfg, create a setup.py file containing:
from dirac_webapp_packaging import extjs_cmdclass
from setuptools import setup
setup(cmdclass=extjs_cmdclass)
If you are building an extension to any of the pages in WebAppDIRAC pyproject.toml file the requires section under build-system must be modified slightly:
[build-system]
# NOTE: Make sure to keep the runtime requirement in setup.cfg in sync with this version
requires = ["dirac_webapp_packaging~=1.0", "WebAppDIRAC ~=4.3.0a0", "setuptools_scm[toml]>=3.4"]
Additionally the dirac extension_metadata entrypoint should be modified to declare the static resources:
import importlib.resources
def extension_metadata():
return {
"priority": NNN,
"web_resources": {
"static": [importlib.resources.files(PKG_NAME) / "WebApp" / "static"],
}
}
Changelog
1.0.1
Switch back to using package_data instead of data_files for distributing assets
1.0.0
Initial release
Metadata
Release files for dirac-webapp-packaging 1.0.1
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 |
|---|---|---|---|---|
| dirac-webapp-packaging-1.0.1.tar.gz | 16.5 kB | Without provenance | Details for dirac-webapp-packaging-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dirac_webapp_packaging-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for dirac_webapp_packaging-1.0.1-py3-none-any.whl |
Total release size: 32.9 kB
Release files / dirac-webapp-packaging-1.0.1.tar.gz
| Download URL | dirac-webapp-packaging-1.0.1.tar.gz |
|---|---|
| Size | 16.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5beb603648ce4b987d8a868d3e6405d03b2b92efd8713a136d508b6108dee97c
|
|
BLAKE2b-256 checksum How to use checksums |
e2bc4c8ec5a71bde848c8d745717faa74e3106947870450f9e22591cc89af8a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/57.0.0 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.9.5
|
Release files / dirac_webapp_packaging-1.0.1-py3-none-any.whl
| Download URL | dirac_webapp_packaging-1.0.1-py3-none-any.whl |
|---|---|
| Size | 16.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
100042b60786d5994ee58c8e028daaabd88f843c027bd1b0f991585506cfba92
|
|
BLAKE2b-256 checksum How to use checksums |
9ab8daf82ff02978a68b6dbc14b6d8fc131ec80275f52ee66ec8547d8314221b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/57.0.0 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.9.5
|
Security for dirac-webapp-packaging 1.0.1
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.