Skip to content

Prepare release 1.10.0 #321

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 22, 2023
Merged

Prepare release 1.10.0 #321

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions doc/changelog.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,13 @@
Changelog
=========

Version 1.10.0 (2023-10-22)
--------------
* Add benchmark for asyncio_webockets
* Expose --min-time from pyperf to pyperformance CLI
* Bump coverage to 7.3.2 for compatibilty with 3.13
* Bump greenlet to 3.0.0rc3 for compatibilty with 3.13

Version 1.0.9 (2023-06-14)
-------------
* Vendor lib2to3 for Python 3.13+
Expand Down
2 changes: 1 addition & 1 deletion pyperformance/__init__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
import sys


VERSION = (1, 0, 9)
VERSION = (1, 10, 0)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just out of curiosity. What made you jump from 0 to 10 in the minor number?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

woo.. it was my mistake.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, so it should have been 1.0.10 then :) What are you going to do? Do you leave as it is or will you withdraw the release and re-release it with the fixed version?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately, it was already released so we decided to keep the current version.
Sorry for the confusion :(

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with that! thanks for the update!

__version__ = '.'.join(map(str, VERSION))


Expand Down