Skip to main content

PyHistory maintains history entries in distributed work environment, which allows many developers to add/remove history entries between releases without conflicts.

Project description

PyHistory

PyPI version PyPI Downloads

App to maintain history file for your project.

PyHistory maintains history entries in distributed work environment, which allows many developers to add/remove history entries between releases without conflicts.

Installation

pip install pyhistory

Features

(All commands can start either with pyhistory or shortcut - pyhi.)

  • Add history entry:

    pyhi add 'New feature'
    pyhi add Something
    
  • List history entries:

    $ pyhi list
    
    * New feature
    * Something
    
  • Update your history file with entries for given release:

    $ cat HISTORY.rst
    my project
    ==========
    
    0.4.1 (2015-08-04)
    ++++++++++++++++++
    
    * Added PyHistory to project.
    * Improved codebase.
    * Other features.
    
    $ pyhi update 0.4.2
    $ cat HISTORY.rst
    my project
    ==========
    
    0.4.2 (2015-08-05)
    ++++++++++++++++++
    
    * Bug fixes
    * Change in API
    * Removed old features
    
    0.4.1 (2015-08-04)
    ++++++++++++++++++
    
    * Added PyHistory to project
    * Improved codebase
    * Other features
    
  • Delete selected entries:

    $ pyhi delete
    
    1. New feature
    2. Something
    3. Another one
    4. Wrong one
    
    (Delete by choosing entries numbers.)
    
    $ pyhi delete 2 4
    $ pyhi list
    
    * New feature
    * Another one
    
  • Clear all history:

    $ pyhi clear
    Do you really want to remove all entries? [y/N]: y
    

    Or without prompt:

    pyhi clear --yes
    

Config file

(setup.cfg has precedence over pyproject.toml for backward compatibility!)

You can adjust Pyhistory behaviour to your needs by adding config to pyproject.toml file:

  [tool.pyhistory]
  history_dir = "some_dir"  # 'history' by default
  history_file = "myhistory.md"  # 'HISTORY.rst' by default
  at_line = 42  # by default history will be injected after first headline

You can also add config to setup.cfg file. Just put pyhistory section in there:

  [pyhistory]
  history_dir = some_dir
  history_file = myhistory.rst
  at_line = 42

Differences in formatting

If you are using markdown format you must note that:

  • Lines are not wrapped, setting for line length is ignored
  • There is extra config for markdown formatting - md_header_level (default is 2) and it sets amount of # in headline for version

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

pyhistory-2.3.0-py2.py3-none-any.whl (8.2 kB view details)

Uploaded Python 2Python 3

File details

Details for the file pyhistory-2.3.0-py2.py3-none-any.whl.

File metadata

  • Download URL: pyhistory-2.3.0-py2.py3-none-any.whl
  • Upload date:
  • Size: 8.2 kB
  • Tags: Python 2, Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.2

File hashes

Hashes for pyhistory-2.3.0-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 edaea79f2cb1973e282212d84d06e8f0e93778cde526e86885afe6330b7ef54a
MD5 20583579a0df105767d00b1bc6531bf1
BLAKE2b-256 3a9030c333159f63f9b98e6fb1f4d47cd151e8aa8ea6a941390f420740c79586

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page