python-asv-bench-memray 0.1.2-2 source package in Ubuntu
Changelog
python-asv-bench-memray (0.1.2-2) unstable; urgency=medium
* Source-only upload.
* d/control: include dh-sequence-python3 to Build-Depends.
* d/rules: include sphinxdoc for buildsystem + remove
doctrees related and symbolic link related lines.
-- Yogeswaran Umasankar <email address hidden> Wed, 17 Jul 2024 21:30:00 +0000
Upload details
- Uploaded by:
- Debian Python Team
- Uploaded to:
- Sid
- Original maintainer:
- Debian Python Team
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Oracular | proposed | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| python-asv-bench-memray_0.1.2-2.dsc | 2.3 KiB | 188ab1c3f99e31daa12f02ce95ede03d6242259902e60e13302d77cfcce49e09 |
| python-asv-bench-memray_0.1.2.orig.tar.gz | 10.1 KiB | e678a6f28cdf6ceecdc2287853f628316fbcc9b0e94e824c6ba4433cd8d1b7d0 |
| python-asv-bench-memray_0.1.2-2.debian.tar.xz | 2.8 KiB | 00a30d715d9a66e88b30101fcdc0dbb1c0e9e30fb21c9a00457f4d39391b9f86 |
Available diffs
- diff from 0.1.2-1 to 0.1.2-2 (971 bytes)
No changes file available.
Binary packages built by this source
- python-asv-bench-memray-doc: Documentation for python-asv-bench-memray
This a proof-of-concept externally defined memray benchmark
plugin for asv. Like all externally defined benchmark plugins
for asv, this has a strict hierarchy. The package name begins
with asv_bench. Benchmarks are defined in a benchmarks folder
under the package module. Each exported new benchmark type has
the export_as_benchmark = [NAMEBenchmark] attribute.
.
This package contains documentation for asv-bench-memray.
- python3-asv-bench-memray: Memray benchmark plugin for asv
This a proof-of-concept externally defined memray benchmark
plugin for asv. Like all externally defined benchmark plugins
for asv, this has a strict hierarchy. The package name begins
with asv_bench. Benchmarks are defined in a benchmarks folder
under the package module. Each exported new benchmark type has
the export_as_benchmark = [NAMEBenchmark] attribute.
