No way to know what changed between versions

[Terseus]

Currently there is no way to know what changed between versions except to download both versions from pypi and check the differences in the source code, this makes very risky to depend on this library for anything non-amateurish.

Please consider adding one or more of the following:

• Release in Github with changelog.
• Annotated tags in the commit where the version is released.
• Add a CHANGELOG.md file to the repo with a header for every version released; bonus points if you follow the Keep a changelog format.
• Add a changelog section in the README.md with a header for every version released.

[emlazzarin]

This is a great idea, but the problem is that the project lacks active maintainers. I have been deputized to help, but am only doing so with a little bit of free time. I think the General Mills team has abandoned the project.

I would welcome such contributions.

On Thu, Oct 27 2022 at 12:49, David Caro < @.*** > wrote:

There is no way currently to know what changed between versions, except to download both of from them from pypi and check the differences in the source code, this makes very risky to depend on this library for anything non-amateurish.

Please consider adding one or more of the following:

• Release in Github with changelog.
• Annotated tags in the commit where the version is released.
• Add a CHANGELOG.md file to the repo with a header for every version released; bonus points if you follow the Keep a changelog format ( https://keepachangelog.com/en/1.0.0/ ).
• Add a changelog section in the README.md with a header for every version released.

— Reply to this email directly, view it on GitHub ( https://github.com/GeneralMills/pytrends/issues/539 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAIWU4OMY3IMH7BXZRX2WE3WFJT35ANCNFSM6AAAAAARP7CAAU ). You are receiving this because you are subscribed to this thread. Message ID: <GeneralMills/pytrends/issues/539 @ github. com>

[kaifman-curve]

Currently there is no way to know what changed between versions except to download both versions from pypi and check the differences in the source code, this makes very risky to depend on this library for anything non-amateurish.

Please consider adding one or more of the following:

• Release in Github with changelog.
• Annotated tags in the commit where the version is released.
• Add a CHANGELOG.md file to the repo with a header for every version released; bonus points if you follow the Keep a changelog format.
• Add a changelog section in the README.md with a header for every version released.

Is there a recent version of Pytrends that is available? The latest version I can see is dated Feb 22 https://pypi.org/project/pytrends/

[Terseus]

Given that @emlazzarin has started doing releases here in Github, I think we can close this now.