Skip to content
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

When will a new version be released? #2294

Closed
CristiFati opened this issue Jun 13, 2024 · 5 comments
Closed

When will a new version be released? #2294

CristiFati opened this issue Jun 13, 2024 · 5 comments
Labels

Comments

@CristiFati
Copy link
Contributor

Sorry for bringing it up here.

Could you please enable discussions for this repo, so any similar questions can be asked there?

@Avasam
Copy link
Collaborator

Avasam commented Aug 3, 2024

You might have better chance at an answer by asking on the mailing list

please do not open github issues for general support requests, or for problems or questions using the modules in this package - they will be closed. For such issues, please email the python-win32 mailing list - note that you must be subscribed to the list before posting.

Although I would also prefer GitHub discussions as they're more accessible and more discoverable.

Now that Python 3.13's first release candidate is out, I think it would be a good time to release pywin32-307 in time for Python 3.13.
I'll sortof highjack this issue to list things I'd personally like to see before next release:

pywin32

Installation and version support

Documentation and examples

These are reference material, it'd be good if they could be accurate / in a working state:

Runtime fixes

Not necessary for a new release imo, so consider these "nice to have"

adodbapi

CC @vernondcole

Installation and version support

Documentation and examples

These are reference material, it'd be good if they could be accurate:

Runtime fixes

@mhammond
Copy link
Owner

mhammond commented Aug 6, 2024

Could you please enable discussions for this repo, so any similar questions can be asked there?

I'd be happy to do that if there was evidence (or even an inkling) that it would be a place where others (ie, not me) would answer questions - but this specific question is the exact opposite of that - it's really directed specifically to me. So I don't see how enabling discussions would help in this specific case?

It's worth considering that one of the reasons for the delay is my time, so adding another venue for things which end up directed specifically to me makes that problem worse, not better. If you feel opening discussions would enable people like yourself to respond to things so I don't have to, I'd be fine to experiment with that, but this specific example is the exact opposite of that.

Re releases, I do need to apologize for having let that slip. I need a new process to make the releases directly from github CI builds, meaning a number of things in previous releases will not be shipped in new ones - most notably the chm documentation and mapi bindings. I'm about to be away from home for over 6 weeks, so I'm afraid to say a new release probably isn't going to happen for at least that long.

Now that Python 3.13's first release candidate is out, I think it would be a good time to release pywin32-307 in time for Python 3.13.

I agree this would be great, but as above, I'm not sure how the timing will work out for that.

I'll sortof highjack this issue to list things I'd personally like to see before next release:

You mean you'd like to see both "in time for 3.13" and that list of items in the next release? To be frank though, I don't think anything in that list should block the next release, except maybe items which block 3.13. I'd rather get back to a regular release cadence. It's worth noting the huge number of cleanup PRs actually works against things here - it both makes the actual issues harder to find, and makes the task of going over them quite daunting. In other words, a doubling of the number of PRs in this repo probably tends to make them get looked at slower rather than faster.

@Avasam
Copy link
Collaborator

Avasam commented Aug 6, 2024

You mean you'd like to see both "in time for 3.13" and that list of items in the next release?

In a perfect world, sure, but I doubt that's realistic. Take it as a wishlist of things I would personally want first if you have the time.
For Python 3.13 support only the following are relevant:

New deprecations and doc fixes are "sooner rather than later", but don't have to be in the next release for Python 3.13 support.

I'd rather get back to a regular release cadence.

Would love to see that, and get bugfixes + documentation improvements in following releases if that's the case.

doubling of the number of PRs in this repo probably tends to make them get looked at slower rather than faster.

Sorry, I didn't want to just forget about something by not posting the PRs. ^^"
There's just so much that I found to be fixed or improved as I'm improving the IntelliSense and infos for checkers for downstream users of pywin32, as well as static checks which revealed tons of existing issues (pywin32 has a lot of historical baggage).
Hence my list above if it helps prioritization, and feel free to prioritize other contributors' PRs over mines.

@mhammond
Copy link
Owner

mhammond commented Oct 4, 2024

I just released 307 taking the PRs @Avasam mentioned above. I'll let it bake for a week or so to see if the new release process actually works, before getting back to the other PRs - after that I intend making more timely releases - sorry for the huge delay here!

@mhammond mhammond closed this as completed Oct 4, 2024
@glyph
Copy link

glyph commented Oct 7, 2024

I just released 307 taking the PRs @Avasam mentioned above. I'll let it bake for a week or so to see if the new release process actually works, before getting back to the other PRs - after that I intend making more timely releases - sorry for the huge delay here!

Thanks for doing this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants