pax_global_header00006660000000000000000000000064145622352570014525gustar00rootroot0000000000000052 comment=d78c8296ed57bd1f50b4ae7839f59bfd49b08105 asv_bench_memray-0.1.2/000077500000000000000000000000001456223525700150275ustar00rootroot00000000000000asv_bench_memray-0.1.2/.github/000077500000000000000000000000001456223525700163675ustar00rootroot00000000000000asv_bench_memray-0.1.2/.github/workflows/000077500000000000000000000000001456223525700204245ustar00rootroot00000000000000asv_bench_memray-0.1.2/.github/workflows/build_docs.yml000066400000000000000000000021151456223525700232550ustar00rootroot00000000000000name: "Build Documentation" on: push: branches: - main # Set a branch name to trigger deployment pull_request: jobs: ci: strategy: fail-fast: false matrix: python-version: [3.12] os: [ubuntu-latest] runs-on: ${{ matrix.os }} permissions: contents: write concurrency: group: ${{ github.workflow }}-${{ github.ref }} steps: - uses: actions/checkout@v4 - uses: actions/setup-python@v4 with: python-version: ${{ matrix.python-version }} - uses: actions/checkout@v3 - name: Install dependencies run: | python -m pip install --upgrade pip pip install sphinx furo sphinx-autodoc2 myst-parser - name: Build docs run: sphinx-build doc/source doc/build/html - name: Deploy Documentation if: ${{ (github.ref == 'refs/heads/main' && github.repository == 'HaoZeke/asv_bench_memray')}} uses: peaceiris/actions-gh-pages@v3 with: github_token: ${{ secrets.GITHUB_TOKEN }} publish_dir: ./doc/build/html asv_bench_memray-0.1.2/.github/workflows/python-publish.yml000066400000000000000000000013161456223525700241350ustar00rootroot00000000000000name: Publish to PyPI on: [push, pull_request] jobs: pypi-publish: runs-on: ubuntu-latest if: github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v') environment: name: pypi url: https://pypi.org/p/asv_bench_memray permissions: id-token: write steps: - uses: actions/checkout@v3 - name: Set up Python uses: actions/setup-python@v3 with: python-version: '3.x' - name: Install dependencies run: | python -m pip install --upgrade pip pip install build - name: Build package run: python -m build - name: Publish package uses: pypa/gh-action-pypi-publish@27b31702a0e7fc50959f5ad993c78deac1bdfc29 asv_bench_memray-0.1.2/.gitignore000066400000000000000000000063511456223525700170240ustar00rootroot00000000000000# Additionally doc/source/apidocs/* doc/build/* ### Generated by gibo (https://github.com/simonwhitaker/gibo) ### https://raw.github.com/github/gitignore/4488915eec0b3a45b5c63ead28f286819c0917de/Python.gitignore # Byte-compiled / optimized / DLL files __pycache__/ *.py[cod] *$py.class # C extensions *.so # Distribution / packaging .Python build/ develop-eggs/ dist/ downloads/ eggs/ .eggs/ lib/ lib64/ parts/ sdist/ var/ wheels/ share/python-wheels/ *.egg-info/ .installed.cfg *.egg MANIFEST # PyInstaller # Usually these files are written by a python script from a template # before PyInstaller builds the exe, so as to inject date/other infos into it. *.manifest *.spec # Installer logs pip-log.txt pip-delete-this-directory.txt # Unit test / coverage reports htmlcov/ .tox/ .nox/ .coverage .coverage.* .cache nosetests.xml coverage.xml *.cover *.py,cover .hypothesis/ .pytest_cache/ cover/ # Translations *.mo *.pot # Django stuff: *.log local_settings.py db.sqlite3 db.sqlite3-journal # Flask stuff: instance/ .webassets-cache # Scrapy stuff: .scrapy # Sphinx documentation docs/_build/ # PyBuilder .pybuilder/ target/ # Jupyter Notebook .ipynb_checkpoints # IPython profile_default/ ipython_config.py # pyenv # For a library or package, you might want to ignore these files since the code is # intended to run in multiple environments; otherwise, check them in: # .python-version # pipenv # According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control. # However, in case of collaboration, if having platform-specific dependencies or dependencies # having no cross-platform support, pipenv may install dependencies that don't work, or not # install all needed dependencies. #Pipfile.lock # poetry # Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control. # This is especially recommended for binary packages to ensure reproducibility, and is more # commonly ignored for libraries. # https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control #poetry.lock # pdm # Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control. #pdm.lock # pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it # in version control. # https://pdm.fming.dev/#use-with-ide .pdm.toml # PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm __pypackages__/ # Celery stuff celerybeat-schedule celerybeat.pid # SageMath parsed files *.sage.py # Environments .env .venv env/ venv/ ENV/ env.bak/ venv.bak/ # Spyder project settings .spyderproject .spyproject # Rope project settings .ropeproject # mkdocs documentation /site # mypy .mypy_cache/ .dmypy.json dmypy.json # Pyre type checker .pyre/ # pytype static type analyzer .pytype/ # Cython debug symbols cython_debug/ # PyCharm # JetBrains specific template is maintained in a separate JetBrains.gitignore that can # be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore # and can be added to the global gitignore or merged into this file. For a more nuclear # option (not recommended) you can uncomment the following to ignore the entire idea folder. #.idea/ .pdm-python asv_bench_memray-0.1.2/CHANGELOG.md000066400000000000000000000014411456223525700166400ustar00rootroot00000000000000# Changelog All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). This project uses [*towncrier*](https://towncrier.readthedocs.io/) and the changes for the upcoming release can be found in . ## [0.1.2](https://github.com/HaoZeke/asv_bench_memray/tree/0.1.2) - 2024-02-11 No significant changes. ## [0.1.1](https://github.com/HaoZeke/asv_bench_memray/tree/0.1.1) - 2024-01-28 No significant changes. ## [0.1.0](https://github.com/HaoZeke/asv_bench_memray/tree/0.1.0) - 2024-01-28 First release. asv_bench_memray-0.1.2/CODEOWNERS000066400000000000000000000010431456223525700164200ustar00rootroot00000000000000# This is a comment. # Each line is a file pattern followed by one or more owners. # These owners will be the default owners for everything in # the repo. Unless a later match takes precedence, # @global-owner1 and @global-owner2 will be requested for # review when someone opens a pull request. * @HaoZeke # Order is important; the last matching pattern takes the most # precedence. When someone opens a pull request that only # modifies JS files, for example, only @js-owner and not the global # owner(s) will be requested for a review. asv_bench_memray-0.1.2/CODE_OF_CONDUCT.md000066400000000000000000000125601456223525700176320ustar00rootroot00000000000000# Contributor Covenant Code of Conduct ## Our Pledge We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. ## Our Standards Examples of behavior that contributes to a positive environment for our community include: * Demonstrating empathy and kindness toward other people * Being respectful of differing opinions, viewpoints, and experiences * Giving and gracefully accepting constructive feedback * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience * Focusing on what is best not just for us as individuals, but for the overall community Examples of unacceptable behavior include: * The use of sexualized language or imagery, and sexual attention or advances of any kind * Trolling, insulting or derogatory comments, and personal or political attacks * Public or private harassment * Publishing others' private information, such as a physical or email address, without their explicit permission * Other conduct which could reasonably be considered inappropriate in a professional setting ## Enforcement Responsibilities Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate. ## Scope This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. ## Enforcement Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [INSERT CONTACT METHOD]. All complaints will be reviewed and investigated promptly and fairly. All community leaders are obligated to respect the privacy and security of the reporter of any incident. ## Enforcement Guidelines Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: ### 1. Correction **Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. **Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. ### 2. Warning **Community Impact**: A violation through a single incident or series of actions. **Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. ### 3. Temporary Ban **Community Impact**: A serious violation of community standards, including sustained inappropriate behavior. **Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. ### 4. Permanent Ban **Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. **Consequence**: A permanent ban from any sort of public interaction within the community. ## Attribution This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC]. For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations]. [homepage]: https://www.contributor-covenant.org [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html [Mozilla CoC]: https://github.com/mozilla/diversity [FAQ]: https://www.contributor-covenant.org/faq [translations]: https://www.contributor-covenant.org/translations asv_bench_memray-0.1.2/LICENSE000066400000000000000000000021551456223525700160370ustar00rootroot00000000000000MIT License Copyright (c) 2024 Rohit Goswami (HaoZeke) Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice (including the next paragraph) shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. asv_bench_memray-0.1.2/README.md000066400000000000000000000047271456223525700163200ustar00rootroot00000000000000# asv_bench_memray This a proof-of-concept externally defined `memray` **benchmark plugin** for `asv`. ## Usage In your `asv.conf.json` add the following to the requirements matrix: ``` json-with-comments "matrix": { "req": { "numpy": ["1.21"], "asv_plugin_memray": [""] }, }, ``` This should be enough for an example like the following to run: ``` python import numpy as np class MyBenchmark: params = [10, int(2e4)] def ray_sum(self, n): self.data = np.random.rand(n) np.sum(self.data) ``` Which should result in something roughly like: ```sh ASV_RUNNER_PATH="../asv_runner" asv run --bench sum · Creating environments....... · Discovering benchmarks ·· Uninstalling from virtualenv-py3.9-asv_bench_memray.._asv_bench_memray-numpy1.21 ·· Building 30a650cb
for virtualenv-py3.9-asv_bench_memray.._asv_bench_memray-numpy1.21. ·· Installing 30a650cb
into virtualenv-py3.9-asv_bench_memray.._asv_bench_memray-numpy1.21 · Running 1 total benchmarks (1 commits * 1 environments * 1 benchmarks) [ 0.00%] · For project commit 30a650cb
: [ 0.00%] ·· Benchmarking virtualenv-py3.9-asv_bench_memray.._asv_bench_memray-numpy1.21 [100.00%] ··· benchmarks.MyBenchmark.ray_sum ok [100.00%] ··· ======== ======= param1 -------- ------- 10 1.72k 20000 162k ======== ======= ASV_RUNNER_PATH="../asv_runner" asv run --bench sum 8.72s user 3.04s system 99% cpu 11.877 total ``` ## Development During development, one needs to pass a relative path: ``` json-with-comments "matrix": { "req": { "asv_bench_memray": ["../asv_bench_memray"] }, }, ``` Also it may be necessary to cleanup older environments and explicitly point to an instance of `asv_runner`: ``` sh rm -rf .asv && ASV_RUNNER_PATH="../asv_runner" asv run --bench sum ``` Personally I keep benchmarks for testing at an [experiments repo](https://github.com/HaoZeke/asv_experiments), but any local test will do. ### Conventions Like all externally defined benchmark plugins for `asv`, this has a strict hierarchy. - [X] The package name begins with `asv_bench` - [X] Benchmarks are defined in a `benchmarks` folder under the package module - [X] Each exported new benchmark type has the `export_as_benchmark = [NAMEBenchmark]` attribute For more conventions follow the documention of `asv_runner`. # License MIT. asv_bench_memray-0.1.2/asv_bench_memray/000077500000000000000000000000001456223525700203315ustar00rootroot00000000000000asv_bench_memray-0.1.2/asv_bench_memray/__init__.py000066400000000000000000000000001456223525700224300ustar00rootroot00000000000000asv_bench_memray-0.1.2/asv_bench_memray/benchmarks/000077500000000000000000000000001456223525700224465ustar00rootroot00000000000000asv_bench_memray-0.1.2/asv_bench_memray/benchmarks/__init__.py000066400000000000000000000000001456223525700245450ustar00rootroot00000000000000asv_bench_memray-0.1.2/asv_bench_memray/benchmarks/raymem.py000066400000000000000000000024761456223525700243230ustar00rootroot00000000000000# SPDX-License-Identifier: MIT # Copyright (c) 2023--present Rohit Goswami # For full license text, see LICENSE file in the root directory of this source tree # or visit https://opensource.org/licenses/MIT import re import tempfile import uuid from pathlib import Path from asv_runner.benchmarks._base import Benchmark from asv_runner.benchmarks._exceptions import NotRequired try: import memray from memray import FileReader except ImportError: raise NotRequired("RayMemBenchmark not requested or memray not found") class RayMemBenchmark(Benchmark): """ A single benchmark for tracking the memory of an object with memray """ name_regex = re.compile("^(Ray[A-Z_].+)|(ray_.+)$") def __init__(self, name, func, attr_sources): Benchmark.__init__(self, name, func, attr_sources) self.type = "memory" self.unit = "bytes" pass def run(self, *param): u_id = uuid.uuid4() temp_dir = tempfile.gettempdir() tfile_loc = Path(f"{temp_dir}/{u_id}.bin") with memray.Tracker( destination=memray.FileDestination(tfile_loc, overwrite=True) ): self.func(*param) freader = FileReader(str(tfile_loc)) return freader.metadata.peak_memory export_as_benchmark = [RayMemBenchmark] asv_bench_memray-0.1.2/doc/000077500000000000000000000000001456223525700155745ustar00rootroot00000000000000asv_bench_memray-0.1.2/doc/changelog.d/000077500000000000000000000000001456223525700177455ustar00rootroot00000000000000asv_bench_memray-0.1.2/doc/changelog.d/+misc.md000066400000000000000000000000611456223525700212720ustar00rootroot00000000000000Harmonize changelog with `asv` and `asv_runner`. asv_bench_memray-0.1.2/doc/changelog.d/readme.md000066400000000000000000000015221456223525700215240ustar00rootroot00000000000000# Usage `towncrier` is used for keeping track of the changelog. The relevant configuration aspects are: - Each file can be formatted using markdown - The contents are rendered in bullets - Each file should be labeled with the corresponding **pull request**, e.g. `NUM.TYPE.md` + Where there is no clear corresponding pull request, `+` can be used instead of `NUM` For mapping the types to headings, the following table can be used: | **TYPE** | **Heading** | | feat | New Features | | api | API Changes | | bugfix | Bug Fixes | | misc | Other Changes and Additions | ## Release ```bash # View the changes towncrier build --draft --version 0.1.0 --date "$(date -u +%Y-%m-%d)" # Modify CHANGES.md towncrier build --version 0.1.0 --date "$(date -u +%Y-%m-%d)" ``` asv_bench_memray-0.1.2/doc/source/000077500000000000000000000000001456223525700170745ustar00rootroot00000000000000asv_bench_memray-0.1.2/doc/source/conf.py000066400000000000000000000027071456223525700204010ustar00rootroot00000000000000# Configuration file for the Sphinx documentation builder. # # For the full list of built-in configuration values, see the documentation: # https://www.sphinx-doc.org/en/master/usage/configuration.html # -- Project information ----------------------------------------------------- # https://www.sphinx-doc.org/en/master/usage/configuration.html#project-information project = 'ASV Memray Benchmark' copyright = '2024, Rohit Goswami' author = 'Rohit Goswami' release = '0.1.2' # -- General configuration --------------------------------------------------- # https://www.sphinx-doc.org/en/master/usage/configuration.html#general-configuration extensions = [ "autodoc2", "myst_parser", "sphinx.ext.intersphinx", "sphinx.ext.viewcode", # Links to source code ] templates_path = ['_templates'] exclude_patterns = [] autodoc2_render_plugin = 'myst' autodoc2_packages = [ "../../asv_bench_memray", ] intersphinx_mapping = { "python": ("https://docs.python.org/3/", None), "sphinx": ("https://www.sphinx-doc.org/en/master", None), "asv": ("https://asv.readthedocs.io/en/latest/", None), "asv_runner": ("https://asv.readthedocs.io/projects/asv-runner/en/latest/", None), } myst_enable_extensions = ["fieldlist", "deflist"] # -- Options for HTML output ------------------------------------------------- # https://www.sphinx-doc.org/en/master/usage/configuration.html#options-for-html-output html_theme = 'furo' html_static_path = ['_static'] asv_bench_memray-0.1.2/doc/source/development.rst000066400000000000000000000016541456223525700221560ustar00rootroot00000000000000Development =========== During development, one needs to pass a relative path: .. code:: json "matrix": { "req": { "asv_bench_memray": ["../asv_bench_memray"] }, }, Also it may be necessary to cleanup older environments and explicitly point to an instance of ``asv_runner``: .. code:: sh rm -rf .asv && ASV_RUNNER_PATH="../asv_runner" asv run --bench sum Personally I keep benchmarks for testing at an `experiments repo `__, but any local test will do. Conventions ----------- 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. For more conventions, follow the documentation of ``asv_runner``. asv_bench_memray-0.1.2/doc/source/index.rst000066400000000000000000000041661456223525700207440ustar00rootroot00000000000000ASV Memray Benchmark Plugin documentation ========================================= ``asv_bench_memray`` is an externally defined ``memray`` benchmark plugin for :doc:`asv ` using :doc:`asv_runner `. .. toctree:: :maxdepth: 2 :caption: Contents: development apidocs/index Usage ===== In your ``asv.conf.json`` add the following to the requirements matrix: .. code:: json "matrix": { "req": { "numpy": ["1.21"], "asv_plugin_memray": [""] }, }, This should be enough for an example like the following to run: .. code:: python import numpy as np class MyBenchmark: params = [10, int(2e4)] def ray_sum(self, n): self.data = np.random.rand(n) np.sum(self.data) Which should result in something roughly like: .. code:: sh ASV_RUNNER_PATH="../asv_runner" asv run --bench sum · Creating environments....... · Discovering benchmarks ·· Uninstalling from virtualenv-py3.9-asv_bench_memray.._asv_bench_memray-numpy1.21 ·· Building 30a650cb
for virtualenv-py3.9-asv_bench_memray.._asv_bench_memray-numpy1.21. ·· Installing 30a650cb
into virtualenv-py3.9-asv_bench_memray.._asv_bench_memray-numpy1.21 · Running 1 total benchmarks (1 commits * 1 environments * 1 benchmarks) [ 0.00%] · For project commit 30a650cb
: [ 0.00%] ·· Benchmarking virtualenv-py3.9-asv_bench_memray.._asv_bench_memray-numpy1.21 [100.00%] ··· benchmarks.MyBenchmark.ray_sum ok [100.00%] ··· ======== ======= param1 -------- ------- 10 1.72k 20000 162k ======== ======= ASV_RUNNER_PATH="../asv_runner" asv run --bench sum 8.72s user 3.04s system 99% cpu 11.877 total .. note:: The GitHub repository at `asv_samples `_ has a dedicated branch for testing ``asv_bench_memray``. License ------- MIT. Indices and tables ================== * :ref:`genindex` * :ref:`modindex` * :ref:`search` asv_bench_memray-0.1.2/pyproject.toml000066400000000000000000000035241456223525700177470ustar00rootroot00000000000000[project] name = "asv_bench_memray" description = "A memray benchmark plugin for asv" authors = [ { name = "Rohit Goswami", email = "rgoswami@ieee.org" }, ] maintainers = [ { name = "Rohit Goswami", email = "rgoswami@ieee.org" }, ] dependencies = [ "memray>=1.7.0", "asv_runner>=0.2.0", ] requires-python = ">=3.8" readme = "README.md" license = {text = "MIT"} dynamic = ["version"] [project.urls] Documentation = "https://haozeke.github.io/asv_bench_memray/" Issues = "https://github.com/HaoZeke/asv_bench_memray/issues" Source = "https://github.com/HaoZeke/asv_bench_memray" [project.optional-dependencies] lint = [ "ruff>=0.0.265", ] rel = [ "tbump", "towncrier", ] [build-system] requires = ["hatchling", "hatch-vcs"] build-backend = "hatchling.build" [tool.hatch.version] source = "vcs" [build.hooks.vcs] version-file = "__init__.py" [tool.ruff] line-length = 88 extend-ignore = [ "E741", # Do not use variables named 'I', 'O', or 'l' ] select = [ "E", # pycodestyle "F", # pyflakes "UP", # pyupgrade "I001", # isort ] [tool.towncrier] package = "asv_bench_memray" package_dir = "asv_bench_memray" all_bullets = false wrap = true directory = "doc/changelog.d" filename = "CHANGELOG.md" start_string = "\n" underlines = ["", "", ""] title_format = "## [{version}](https://github.com/HaoZeke/asv_bench_memray/tree/{version}) - {project_date}" issue_format = "[#{issue}](https://github.com/HaoZeke/asv_bench_memray/issues/{issue})" [[tool.towncrier.type]] directory = "feat" name = "New Features" showcontent = true [[tool.towncrier.type]] directory = "api" name = "API Changes" showcontent = true [[tool.towncrier.type]] directory = "bugfix" name = "Bug Fixes" showcontent = true [[tool.towncrier.type]] directory = "misc" name = "Other Changes and Additions" showcontent = true asv_bench_memray-0.1.2/tbump.toml000066400000000000000000000017651456223525700170640ustar00rootroot00000000000000# Uncomment this if your project is hosted on GitHub: # github_url = "https://github.com///" [version] current = "0.1.2" # Example of a semver regexp. # Make sure this matches current_version before # using tbump regex = ''' (?P\d+) \. (?P\d+) \. (?P\d+) ''' [git] message_template = "REL: Bump to {new_version}" tag_template = "v{new_version}" # For each file to patch, add a [[file]] config # section containing the path of the file, relative to the # tbump.toml location. [[file]] src = "doc/source/conf.py" # You can specify a list of commands to # run after the files have been patched # and before the git commit is made [[before_commit]] name = "Make changelog" cmd = "towncrier build --version={new_version}" [[before_commit]] name = "Check changelog" cmd = "grep -q {new_version} CHANGELOG.md" # Or run some commands after the git tag and the branch # have been pushed: # [[after_push]] # name = "publish" # cmd = "./publish.sh"