-
Notifications
You must be signed in to change notification settings - Fork 388
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.
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
Release 6.0.0 to allow users to update to Python 3.12? #793
Comments
This pr needs to be merged before this version #788 |
@jairhenrique just to understand: "needs" as in "would be beneficial" or as in "hard blocker"? Could you elaborate? |
@hartwork I think it's a hard blocker because of this comment #784 (comment). More people may need to recreate the cassettes if this change doesn't go through. |
@jairhenrique thanks for elaborating, I understand! 👍 @parkerhancock if you could rebase your pull request #788 against latest |
@kevin1024 I believe all release blockers are resolved now. |
What is the highest Python version that you recommend to use ATM? |
@anton-daneyko-ultramarin probably 3.11? Could you elaborate or give more context for the question? |
@hartwork I am about to give 3.10 a try, but decided to ask you instead. I assumed it's something easy to answer. |
@anton-daneyko-ultramarin thanks for elaborating! Could you check if the pickle issue is the same as #737? If not, please create a new issue with details. Thanks in advance! |
I'm running a big regression test with the latest vcrpy development head. I'll update this comment when it is done ( likely in the morning EST ) if i run across any issues :) Update: 👍 My big regression test did not uncover any sort of issues with the current head 713cb36d35108a21416744a393f3c947b86a0efe |
Any update on when we'll have the new release? |
@kevin1024 we need you here to move forward. Do you have a minute? |
Hey guys! Are there any plans to release that stuff soon? I need fixes for |
@kevin1024 we need you here to move forward. Do you have a minute? |
I'd like to get #801 in before 6.0 |
OK! lemme cut a release. |
No worries, ping me when fixed and I'll do another release. |
I did not have the chance to look into it back then and now I am getting bitten by this error again. I get a Tail of a stack trace
|
@anton-daneyko-ultramarin let me repeat, please create a new issue, your report is out of place here. Thank you! |
Hi! 👋
(This is similar to issue #749 for the release of VCR.py 5.1.0.)
Since release 5.1.0 I believe we have merged the following pull requests to
master
(in order of pull request ID):tests/assertions.py
(fixes #773) #789I believe it would be important to do a soon new release 6.0.0 to allow users to upgrade to Python 3.12 which VCR.py has been de-facto blocking (including one of my own projects, case hartwork/wnpp.debian.net#806).
For anyone wondering why 6.0.0 rather than 5.2.0, we agreed at #731 (comment) that merge of now-merged #731 should go along with a bump in major version.
@kevin1024 would you be up for cutting a release 6.0.0 from latest
master
shortly?(Latest commit is 6a31904 as of the moment.)
Thanks and best, Sebastian
CC @jairhenrique
The text was updated successfully, but these errors were encountered: