PackageTrack Sign in Track my project

deprecation

A library to handle automated deprecations

2.1.0 99M downloads/mo #347 most downloaded on PyPI briancurtin/deprecation

What this package is like to depend on

Last release 6 years ago

no release in 18 months

Release timing varies

gaps range from 2 weeks to 11 months

This project publishes no release notes

the list below is its commits, not an announcement

Nothing withdrawn

no release was ever pulled

10 years old

13 releases · first in 2017

0 releases in the last 12 months

see the full history below

Release timeline

13 releases · Jan 2017 to Apr 2020
2018 2019 2020 2021 2022 2023 2024 2025 2026
Release Pre-release

Releases

latest 13
  1. 2.1.0 20 Apr 2020
    Commits, not release notes

    This project publishes no release notes. Between 2.0.7 and 2.1.0 there were 4 commits, 4 of them substantive:

    • Comment out non-existent html_static_path in doc (#41)
    • Remove an invalid escape sequence \s from pydoc (#45)
    • Allow removed_in to be a date (#47)
    • Added line @functools.wraps(method) to the fail_if_not_removed decorator, which should fix https://github.com/briancurtin/deprecation/issues/42 (#48)
  2. 2.0.7 12 Aug 2019
    Commits, not release notes

    This project publishes no release notes. Between 2.0.6 and 2.0.7 there were 2 commits, 1 of them substantive:

    • Include docs in source distributions, fixes #39 (#40)
  3. 2.0.6 26 Sep 2018
    Commits, not release notes

    This project publishes no release notes. Between 2.0.5 and 2.0.6 there were 3 commits, 2 of them substantive:

    • Build universal wheels (#33)
    • Pass args onto DeprecationWarning initializer (#37)
  4. 2.0.5 02 Jul 2018
    Commits, not release notes

    This project publishes no release notes. Between 2.0.4 and 2.0.5 there were 3 commits, 2 of them substantive:

    • Fix unit tests hiding in nose by fail_if_not_removed (#31)
    • Add comment about nose naming requirement, Issue #32
  5. 2.0.4 20 Jun 2018
    Commits, not release notes

    This project publishes no release notes. Between 2.0.3 and 2.0.4 there were 3 commits, 2 of them substantive:

    • Begin 2.0.4 work
    • Move sample.py out of the distribution (#29)
  6. 2.0.3 08 Jun 2018
    Commits, not release notes

    This project publishes no release notes. Between 2.0.2 and 2.0.3 there were 9 commits, 7 of them substantive:

    • Fix URLs over length in setup
    • Make deprecation.version the source of truth (#23)
    • Include sample in installation for proper docs build (#24)
    • Remove Python 3.4 from testing (#25)
    • Remove 3.4 from setup as well
    • Remove Python 3.4 from testing (#25)
    • Reference the sample module more obviously (#26)
  7. 2.0.2 12 Apr 2018
    Commits, not release notes

    This project publishes no release notes. Between 2.0.1 and 2.0.2 there were 2 commits, 1 of them substantive:

    • Include tests in PyPI tarball (#19)
  8. 2.0.1 10 Apr 2018
    Commits, not release notes

    This project publishes no release notes. Between 2.0 and 2.0.1 there were 1 commits, 1 of them substantive:

    • Add links to Github for source and bug tracker
  9. 2.0 21 Feb 2018
    Commits, not release notes

    This project publishes no release notes. Between 1.2 and 2.0 there were 4 commits, 3 of them substantive:

    • Improve warning message handling of None parts (#14)
    • Use deprecated-directive in docstring, add message_location (#15)
    • Add a docstring for message_location (#16)
  10. 1.2 19 Feb 2018

    Nothing published for this version

  11. 1.1 01 Feb 2018

    Nothing published for this version

  12. 1.0.1 02 May 2017

    Nothing published for this version

  13. 1.0 23 Jan 2017

    Nothing published for this version

Stop reading changelogs one package at a time.

Point PackageTrack at your project and get told which of your dependencies moved, which of those matter, and what to do about it.

Track my project