| Name | vulcan-py JSON |
| Version |
2.1.0
JSON |
| download |
| home_page | |
| Summary | Tool for leveraging lockfiles to pin dependencies in wheels and sdists |
| upload_time | 2023-07-25 14:38:00 |
| maintainer | |
| docs_url | None |
| author | |
| requires_python | >=3.8 |
| license | Apache License Version 2.0 |
| keywords |
build
tooling
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
---
Vulcan supports building python>=3.6. Vulcan itself may only be installed in python>=3.8.
The recommended installation is via pipx. This will save a lot of pain with respect to conflicting versions,
as well as having multiple python versions in various projects.
---
[//]: # ( TODO: build status indicator here )
Vulcan is a build tool intended to make lockfiles without having to force users to deal with a bunch of setup
in ci systems and their own projects. The intended workflow is that users will use create a lockfile with
`vulcan lock`, then vulcan will use that lockfile to transparently set patch-version pinned requirements
to avoid incidents related to transitive dependencies being implicitly upgraded.
## Warn:
Vulcan is NOT an example project, do not blindly copy/paste from any files in this project except the
README.md. This project builds itself and therefore requires some special configurations.
# Getting started
---
For instructions on how to migrate existing projects to vulcan, see [MIGRATING.md](./MIGRATING.md)
## Install vulcan (recommended)
The recommended installation method is pipx, to avoid the dependencies in vulcan conflicting with the
dependencies in your application:
```bash
$ pip install pipx-in-pipx # if you don't already have pipx installed
$ pipx install vulcan-py[cli,convert]
```
## Minimal starting configuration (pyproject.toml)
```toml
[project]
name = "package_name"
dynamic = ['version']
# This section is mandatory and may be blindly copy/pasted
[build-system]
requires = ['vulcan-py']
build-backend = "vulcan.build_backend"
```
## Vulcan configuration
Vulcan uses setuptools internally, so any configuration specified in the
[setuptools pyproject.toml config](https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html) will
be respected here.
In addition, there are some vulcan-specific configurations which may be specified under `[tool.vulcan]`:
### no-lock
If set, ignore the lockfile when building wheels and installing locally. It is an error to use no-lock with a
shiv build. This may be overridden with `vulcan build --no-lock` or `vulcan build --lock`.
Generally, no-lock should be used with libraries, and should not be used with applications. This is due to the
fact that having multiple libraries with locked dependencies tends to be very difficult, with the locked
dependencies conflicting almost immediately.
```toml
[tool.vulcan]
no-lock = true
```
### lockfile
If set, allows you to specify the name of the lockfile. Defaults to `vulcan.lock`
```toml
[tool.vulcan]
lockfile = "vulcan-2.lock"
```
### python-lock-with
By default, vulcan decides which python to use to generate a lockfile based on the currently active
virtualenv. If there is not a currently active virtualenv, it will default to whichever version of python
vulcan itself was installed with. Both of these behaviors can be overridden with the `python-lock-with` key,
which specifies which python should be used to lock
```toml
[tool.vulcan]
python-lock-with = "3.9"
```
### plugins
Vulcan supports plugins, which can be called as a part of the build system to do some action on the
in-progress build. These are registered via [entry points](https://github.com/optiver/vulcan-py#plugins), and
to ensure there are not any accidental plugins activated they must be specified in the plugins config argument
as well.
```toml
[tool.vulcan]
plugins = ["plug1", "plug2"]
```
### shiv
This repeatable section allows configuration of a shiv command to be called when invoking `vulcan build --shiv`.
There are some mandatory keys, and some optional keys available.
Note the double brackets, this is what makes the section repeatable.
```toml
[[tool.vulcan.shiv]]
bin_name = "output_binary_name" # mandatory
console_script = "console_script_name" #| Pick exactly one of
entry_point = "path.to.entry_point:main" #|
interpreter = "/usr/bin/env python3.9" # optional
with_extras = ["extra1", "another_extra"] # optional
extra_args = "--any --other --shiv --arguments"
```
### dependencies
This and the next section make the core of vulcan's functionality. These are the top-level unlocked
dependencies for your application or library. With no-lock, these are translated directly into wheel
dependencies without modification. Normally, these are used to determine the contents of the lockfile.
```toml
[tool.vulcan.dependencies]
requests="" # no specific version
lxml="~=4.0" # with a version specification
'build[virtualenv]' = "" # with extras
# build = {version="", extras=["virtualenv"]} # different way of specifying extras
```
Note that if this section is specified, it is REQUIRED to put "dependencies" into the `dynamic` key in the
`[project]` section of pyproject.toml
### extras
This section is similar to the above section, and is used to specify additional extras your application may
provide. These are also used in resolving the lockfile if no-lock is not present, and it must be possible to
install all extras at the same time.
```toml
[tool.vulcan.extras]
extra1 = ["requests[socks]~=2.0"]
extra2 = ["click"]
```
### dev-dependencies
Finally, this section is used to specify any dependencies used for development, such as mypy or pytest. These
are NOT used in resolving the lockfile, and are installed when `vulcan develop` is run (in addition to
installing the application as an editable install, equivalent to `pip install -e .`). It is possible to only
install a single set of dev dependencies with `vulcan develop {key}` (e.x `vulcan develop static-analysis`)
```toml
[tool.vulcan.dev-dependencies.test]
pytest=""
coverage=""
pytest-asyncio=""
[tool.vulcan.dev-dependencies.static-analysis]
flake8=""
mypy=""
types-dataclasses=""
```
## Build the package
Assuming the above has worked, you should now be able to do the following:
```bash
$ vulcan build --wheel
```
And find a wheel in `dist/package_name-0.0.0-py3-none-any.whl`
# Command Overview
---
## build
```
$ vulcan build --help
usage: vulcan build [-h] [--sdist | --wheel | --shiv] [-o OUTDIR]
optional arguments:
-h, --help show this help message and exit
--sdist
--wheel
--shiv
-o OUTDIR, --outdir OUTDIR
```
Vulcan build gives a way to create wheels, sdists, and shiv applications. Instead of having the following in
tox.ini:
```
shiv -p '/usr/bin/env python3.6' -e your_application.__main__:run -o {distdir}/binary_name" --compile-pyc .
```
You can instead have only
```
vulcan build --shiv -o {distdir}
```
and have the actual configuration for that command in your pyproject.toml:
```toml
[[tool.vulcan.shiv]]
bin_name="binary_name"
entry_point="your_application.__main__:run"
interpreter="/usr/bin/env python3.6"
extra_args="--compile-pyc"
```
This section may be repeated, in which case `build` will create all the specified binaries.
`build` also supports outputting wheel and sdists, which can be used to distribute your application as a pip
package as well as a shiv binary if desired.
## lock
```
$ vulcan lock --help
usage: vulcan lock [-h]
optional arguments:
-h, --help show this help message and exit
```
Vulcan lock supports no arguments (except --help) and takes no options. This command takes the dependencies
specified in `[tool.vulcan.dependencies]` and resolves them into a set of patch-version pinned dependencies,
then writes that into `vulcan.lock` (lockfile is configurable with the `lockfile` setting under `[tool.vulcan]`).
This command will update any dependencies that have had new releases (compatible with your dependencies and
all other package's requirements), and will error if it is not possible to find a resolution. This should not
be done automatically, and should always involve some extra testing when used (since the dependencies are
being updated and may introduce a bug).
## add
`add` is a convenience tool that will grab the most recent version of a library, add it to the pyproject.toml,
and regenerate the lockfile (if applicable)
```
$ vulcan add --help
usage: vulcan add [-h] [--no-lock] reqspec
positional arguments:
reqspec
optional arguments:
-h, --help show this help message and exit
--no-lock
```
## develop
```
$ vulcan develop --help
usage: vulcan develop [-h]
optional arguments:
-h, --help show this help message and exit
```
`develop` is a convenience tool intended to replicate the effects of `pip install -e .` when developing an
application, as that command was [removed in pep 517](https://www.python.org/dev/peps/pep-0517/#get-requires-for-build-sdist).
If you did not previously use `pip install -e .`, this command may be safely ignored. If you did, follow these
steps (assuming you have already created the lockfile) to update your development environment to use `develop`:
```
$ pip uninstall your_package_name
$ vulcan develop
```
# Plugins
Vulcan supports a minimal plugin mechanism, which can be used to trigger arbitrary build steps during the
build process.
## vulcan.pre_build
Pre-build steps take place immediately before creating the wheel or sdist output. As an example, you could
have a plugin that populates a target file with the build time:
```python
# myplugin.py
from typing import Optional, Dict
from pathlib import Path
from datetime import datetime
def populate_buildtime(config: Optional[Dict[str, str]]) -> None:
assert config is not None
assert 'target' in config
Path(config['target']).write_text(f'{datetime.now():%Y-%m-%d %H:%M}')
```
```toml
# in the plugin's pyproject.toml
[project.entry-points."vulcan.pre_build"]
myplugin="myplugin:populate_datetime"
```
```toml
# in the project's pyproject.toml
[tool.vulcan]
plugins = ["myplugin"]
[tool.vulcan.plugin.myplugin]
target = "myproject/__BUILD_TIME__"
```
# Tips
---
## Pinning vulcan deps
As vulcan itself is not pinned, it is theoretically possible for an upstream dependency of vulcan to introduce
a bug. If you would like to eliminate this possibility, you can add an extra to your application that pins
vulcan, which will lock in the dependencies of vulcan itself. Something along the lines of:
```toml
[tool.vulcan.extras]
build = ["vulcan~=1.2"]
```
And then install your tox build job with a configuration that includes the line:
```ini
[toxenv:build]
extras =
build
```
And this will ensure that vulcan and all its dependencies are pinned in your lockfile and used while building.
# License
---
vulcan is:
Copyright 2021 Optiver IP B.V.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
```
http://www.apache.org/licenses/LICENSE-2.0
```
Unless required by applicable law or explicitly agreed by an authorized representative of Optiver IP B.V. in
writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
CONDITIONS OF ANY KIND, either express or implied. Please see the License for the specific language governing
permissions and limitations under the License.
## tox and vulcan
To make sure that tox and vulcan can interact comfortably, be sure to add your `vulcan.lock` to your `MANIFEST.in`.
This will ensure that while building your package, tox also picks up the locked dependencies.
# Migrating
Vulcan contains 2 conversion scripts: convert_pep621, and convert_vulcan2.
The first script will convert any non-pyproject.toml project into vulcan and pyproject.toml.
The second will convert vulcan~=1 projects into vulcan 2.
These scripts are for convenience and provided as best-effort only, and may not perfectly convert all possible projects.
Raw data
{
"_id": null,
"home_page": "",
"name": "vulcan-py",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": "",
"keywords": "build,tooling",
"author": "",
"author_email": "Joel Christiansen <joelchristiansen@optiver.com>",
"download_url": "https://files.pythonhosted.org/packages/45/fd/bd8f05e4dbb1eec5f2cb661ddff2b1faf87ab73772178cfeb09173658700/vulcan-py-2.1.0.tar.gz",
"platform": null,
"description": "\n\n---\n\nVulcan supports building python>=3.6. Vulcan itself may only be installed in python>=3.8. \nThe recommended installation is via pipx. This will save a lot of pain with respect to conflicting versions,\nas well as having multiple python versions in various projects.\n\n---\n\n[//]: # ( TODO: build status indicator here )\n\nVulcan is a build tool intended to make lockfiles without having to force users to deal with a bunch of setup \nin ci systems and their own projects. The intended workflow is that users will use create a lockfile with \n`vulcan lock`, then vulcan will use that lockfile to transparently set patch-version pinned requirements \nto avoid incidents related to transitive dependencies being implicitly upgraded.\n\n## Warn:\n\nVulcan is NOT an example project, do not blindly copy/paste from any files in this project except the\nREADME.md. This project builds itself and therefore requires some special configurations.\n\n# Getting started\n\n---\n\nFor instructions on how to migrate existing projects to vulcan, see [MIGRATING.md](./MIGRATING.md)\n\n## Install vulcan (recommended)\n\nThe recommended installation method is pipx, to avoid the dependencies in vulcan conflicting with the \ndependencies in your application:\n\n```bash\n$ pip install pipx-in-pipx # if you don't already have pipx installed\n$ pipx install vulcan-py[cli,convert]\n```\n\n## Minimal starting configuration (pyproject.toml)\n\n```toml\n[project]\nname = \"package_name\"\ndynamic = ['version']\n\n# This section is mandatory and may be blindly copy/pasted\n[build-system]\nrequires = ['vulcan-py']\nbuild-backend = \"vulcan.build_backend\"\n```\n\n## Vulcan configuration\n\nVulcan uses setuptools internally, so any configuration specified in the \n[setuptools pyproject.toml config](https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html) will\nbe respected here.\n\nIn addition, there are some vulcan-specific configurations which may be specified under `[tool.vulcan]`:\n\n### no-lock\n\nIf set, ignore the lockfile when building wheels and installing locally. It is an error to use no-lock with a\nshiv build. This may be overridden with `vulcan build --no-lock` or `vulcan build --lock`.\n\nGenerally, no-lock should be used with libraries, and should not be used with applications. This is due to the\nfact that having multiple libraries with locked dependencies tends to be very difficult, with the locked\ndependencies conflicting almost immediately.\n\n```toml\n[tool.vulcan]\nno-lock = true\n```\n\n### lockfile\n\nIf set, allows you to specify the name of the lockfile. Defaults to `vulcan.lock`\n\n```toml\n[tool.vulcan]\nlockfile = \"vulcan-2.lock\"\n```\n\n### python-lock-with\n\nBy default, vulcan decides which python to use to generate a lockfile based on the currently active\nvirtualenv. If there is not a currently active virtualenv, it will default to whichever version of python\nvulcan itself was installed with. Both of these behaviors can be overridden with the `python-lock-with` key,\nwhich specifies which python should be used to lock\n\n```toml\n[tool.vulcan]\npython-lock-with = \"3.9\"\n```\n\n### plugins\n\nVulcan supports plugins, which can be called as a part of the build system to do some action on the\nin-progress build. These are registered via [entry points](https://github.com/optiver/vulcan-py#plugins), and\nto ensure there are not any accidental plugins activated they must be specified in the plugins config argument\nas well.\n\n```toml\n[tool.vulcan]\nplugins = [\"plug1\", \"plug2\"]\n```\n\n### shiv\n\nThis repeatable section allows configuration of a shiv command to be called when invoking `vulcan build --shiv`.\nThere are some mandatory keys, and some optional keys available.\n\nNote the double brackets, this is what makes the section repeatable.\n\n```toml\n[[tool.vulcan.shiv]]\nbin_name = \"output_binary_name\" # mandatory\nconsole_script = \"console_script_name\" #| Pick exactly one of\nentry_point = \"path.to.entry_point:main\" #|\ninterpreter = \"/usr/bin/env python3.9\" # optional\nwith_extras = [\"extra1\", \"another_extra\"] # optional\nextra_args = \"--any --other --shiv --arguments\"\n```\n\n\n### dependencies\n\nThis and the next section make the core of vulcan's functionality. These are the top-level unlocked\ndependencies for your application or library. With no-lock, these are translated directly into wheel\ndependencies without modification. Normally, these are used to determine the contents of the lockfile.\n\n```toml\n[tool.vulcan.dependencies]\nrequests=\"\" # no specific version\nlxml=\"~=4.0\" # with a version specification\n'build[virtualenv]' = \"\" # with extras\n# build = {version=\"\", extras=[\"virtualenv\"]} # different way of specifying extras\n```\n\nNote that if this section is specified, it is REQUIRED to put \"dependencies\" into the `dynamic` key in the\n`[project]` section of pyproject.toml\n\n### extras\n\nThis section is similar to the above section, and is used to specify additional extras your application may\nprovide. These are also used in resolving the lockfile if no-lock is not present, and it must be possible to\ninstall all extras at the same time.\n\n```toml\n[tool.vulcan.extras]\nextra1 = [\"requests[socks]~=2.0\"]\nextra2 = [\"click\"]\n```\n\n### dev-dependencies\n\nFinally, this section is used to specify any dependencies used for development, such as mypy or pytest. These\nare NOT used in resolving the lockfile, and are installed when `vulcan develop` is run (in addition to\ninstalling the application as an editable install, equivalent to `pip install -e .`). It is possible to only\ninstall a single set of dev dependencies with `vulcan develop {key}` (e.x `vulcan develop static-analysis`)\n\n```toml\n[tool.vulcan.dev-dependencies.test]\npytest=\"\"\ncoverage=\"\"\npytest-asyncio=\"\"\n\n[tool.vulcan.dev-dependencies.static-analysis]\nflake8=\"\"\nmypy=\"\"\ntypes-dataclasses=\"\"\n```\n\n## Build the package\n\n\nAssuming the above has worked, you should now be able to do the following:\n\n```bash\n$ vulcan build --wheel\n```\n\nAnd find a wheel in `dist/package_name-0.0.0-py3-none-any.whl`\n\n# Command Overview\n\n---\n\n## build\n\n```\n$ vulcan build --help\nusage: vulcan build [-h] [--sdist | --wheel | --shiv] [-o OUTDIR]\n\noptional arguments:\n -h, --help show this help message and exit\n --sdist\n --wheel\n --shiv\n -o OUTDIR, --outdir OUTDIR\n```\n\nVulcan build gives a way to create wheels, sdists, and shiv applications. Instead of having the following in\ntox.ini:\n```\nshiv -p '/usr/bin/env python3.6' -e your_application.__main__:run -o {distdir}/binary_name\" --compile-pyc .\n```\n\nYou can instead have only \n```\nvulcan build --shiv -o {distdir}\n```\nand have the actual configuration for that command in your pyproject.toml:\n\n```toml\n[[tool.vulcan.shiv]]\nbin_name=\"binary_name\"\nentry_point=\"your_application.__main__:run\"\ninterpreter=\"/usr/bin/env python3.6\"\nextra_args=\"--compile-pyc\"\n```\n\nThis section may be repeated, in which case `build` will create all the specified binaries.\n\n`build` also supports outputting wheel and sdists, which can be used to distribute your application as a pip\npackage as well as a shiv binary if desired.\n\n## lock\n\n```\n$ vulcan lock --help\n\nusage: vulcan lock [-h]\n\noptional arguments:\n -h, --help show this help message and exit\n```\n\nVulcan lock supports no arguments (except --help) and takes no options. This command takes the dependencies\nspecified in `[tool.vulcan.dependencies]` and resolves them into a set of patch-version pinned dependencies,\nthen writes that into `vulcan.lock` (lockfile is configurable with the `lockfile` setting under `[tool.vulcan]`).\n\nThis command will update any dependencies that have had new releases (compatible with your dependencies and\nall other package's requirements), and will error if it is not possible to find a resolution. This should not\nbe done automatically, and should always involve some extra testing when used (since the dependencies are\nbeing updated and may introduce a bug).\n\n## add\n\n`add` is a convenience tool that will grab the most recent version of a library, add it to the pyproject.toml,\nand regenerate the lockfile (if applicable)\n\n```\n$ vulcan add --help \nusage: vulcan add [-h] [--no-lock] reqspec \n \npositional arguments: \n reqspec \n \noptional arguments: \n -h, --help show this help message and exit \n --no-lock \n```\n\n\n## develop\n\n```\n$ vulcan develop --help\nusage: vulcan develop [-h]\n\noptional arguments:\n -h, --help show this help message and exit\n```\n\n`develop` is a convenience tool intended to replicate the effects of `pip install -e .` when developing an\napplication, as that command was [removed in pep 517](https://www.python.org/dev/peps/pep-0517/#get-requires-for-build-sdist).\n\nIf you did not previously use `pip install -e .`, this command may be safely ignored. If you did, follow these\nsteps (assuming you have already created the lockfile) to update your development environment to use `develop`:\n\n```\n$ pip uninstall your_package_name\n$ vulcan develop\n```\n\n# Plugins\n\nVulcan supports a minimal plugin mechanism, which can be used to trigger arbitrary build steps during the\nbuild process.\n\n## vulcan.pre_build\n\nPre-build steps take place immediately before creating the wheel or sdist output. As an example, you could\nhave a plugin that populates a target file with the build time:\n\n```python\n# myplugin.py\nfrom typing import Optional, Dict\nfrom pathlib import Path\nfrom datetime import datetime\ndef populate_buildtime(config: Optional[Dict[str, str]]) -> None:\n assert config is not None\n assert 'target' in config\n Path(config['target']).write_text(f'{datetime.now():%Y-%m-%d %H:%M}')\n```\n\n```toml\n# in the plugin's pyproject.toml\n[project.entry-points.\"vulcan.pre_build\"]\nmyplugin=\"myplugin:populate_datetime\"\n```\n\n```toml\n# in the project's pyproject.toml\n[tool.vulcan]\nplugins = [\"myplugin\"]\n\n[tool.vulcan.plugin.myplugin]\ntarget = \"myproject/__BUILD_TIME__\"\n```\n\n# Tips\n\n---\n\n## Pinning vulcan deps\nAs vulcan itself is not pinned, it is theoretically possible for an upstream dependency of vulcan to introduce\na bug. If you would like to eliminate this possibility, you can add an extra to your application that pins\nvulcan, which will lock in the dependencies of vulcan itself. Something along the lines of:\n\n```toml\n[tool.vulcan.extras]\nbuild = [\"vulcan~=1.2\"]\n```\n\nAnd then install your tox build job with a configuration that includes the line:\n\n```ini\n[toxenv:build]\nextras = \n build\n```\n\nAnd this will ensure that vulcan and all its dependencies are pinned in your lockfile and used while building.\n\n# License\n\n---\n\nvulcan is:\n\nCopyright 2021 Optiver IP B.V.\n\nLicensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance\nwith the License. You may obtain a copy of the License at\n\n```\nhttp://www.apache.org/licenses/LICENSE-2.0\n```\n\nUnless required by applicable law or explicitly agreed by an authorized representative of Optiver IP B.V. in\nwriting, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR\nCONDITIONS OF ANY KIND, either express or implied. Please see the License for the specific language governing\npermissions and limitations under the License.\n\n\n## tox and vulcan\n\nTo make sure that tox and vulcan can interact comfortably, be sure to add your `vulcan.lock` to your `MANIFEST.in`. \nThis will ensure that while building your package, tox also picks up the locked dependencies.\n\n\n# Migrating\n\nVulcan contains 2 conversion scripts: convert_pep621, and convert_vulcan2. \nThe first script will convert any non-pyproject.toml project into vulcan and pyproject.toml. \nThe second will convert vulcan~=1 projects into vulcan 2. \nThese scripts are for convenience and provided as best-effort only, and may not perfectly convert all possible projects.\n",
"bugtrack_url": null,
"license": "Apache License Version 2.0",
"summary": "Tool for leveraging lockfiles to pin dependencies in wheels and sdists",
"version": "2.1.0",
"project_urls": {
"github": "https://github.com/optiver/vulcan-py"
},
"split_keywords": [
"build",
"tooling"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "7b132a570849327eed1274cdf6d6b6d2b5feb247f98aa55971110bc315560352",
"md5": "763c53aea4ec45f48e159e67c219a64e",
"sha256": "f5062e5d247d9ebecf00f25b575b0ac879b0c4b83b4c026d6b6e10ee467c6c30"
},
"downloads": -1,
"filename": "vulcan_py-2.1.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "763c53aea4ec45f48e159e67c219a64e",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 25731,
"upload_time": "2023-07-25T14:37:58",
"upload_time_iso_8601": "2023-07-25T14:37:58.662798Z",
"url": "https://files.pythonhosted.org/packages/7b/13/2a570849327eed1274cdf6d6b6d2b5feb247f98aa55971110bc315560352/vulcan_py-2.1.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "45fdbd8f05e4dbb1eec5f2cb661ddff2b1faf87ab73772178cfeb09173658700",
"md5": "b9252b0d72f23a8881525f94430cf97c",
"sha256": "42de1fe2e991f807cb342998800e9688c01a458ed8eb2b9af9db220debb97edc"
},
"downloads": -1,
"filename": "vulcan-py-2.1.0.tar.gz",
"has_sig": false,
"md5_digest": "b9252b0d72f23a8881525f94430cf97c",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 26716,
"upload_time": "2023-07-25T14:38:00",
"upload_time_iso_8601": "2023-07-25T14:38:00.268567Z",
"url": "https://files.pythonhosted.org/packages/45/fd/bd8f05e4dbb1eec5f2cb661ddff2b1faf87ab73772178cfeb09173658700/vulcan-py-2.1.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-07-25 14:38:00",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "optiver",
"github_project": "vulcan-py",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"tox": true,
"lcname": "vulcan-py"
}
