Comments (3)
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.
from pywin32.
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
- #2349 or some variant. As it opens the door to speeding up deployments (wheels can be taken directly from CI artefacts instead of rebuilding everything locally). And other build/setup modernization
- Removing code paths incompatible with Python 3.13: #2312
- Finishing the Python unicode cleanup: #2343
- Another extremely old deprecation: #2344
- New deprecations:
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
- Removing code paths incompatible with Python 3.13: #2311
Documentation and examples
These are reference material, it'd be good if they could be accurate:
- Decide where the adodbapi changelog should go and its version bump: #2352
- Fix misplaced docstrings: #2250 OR #2307
- #2347
Runtime fixes
from pywin32.
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.
from pywin32.
Related Issues (20)
- Does it support winUI3 HOT 1
- Scripting with win32api fails in Python 3.12 HOT 10
- Exposing RealGetWindowClass
- 'win32ui' has no attribute 'CreatePrinterDC' HOT 1
- where the fuck is win32crypt HOT 5
- Client missing? HOT 1
- __import_pywin32_system_module_ function is not finding pywintypesXX.dll even if it exists HOT 1
- Last error code errorneously set by some modules
- Free-threaded support? HOT 3
- Missing support for record pointers as method parameters of a Dispatch Interface.
- Support for MFC's dynamic layout in win32ui
- Unable to install directly from Git via pip HOT 1
- Can't find pywintypes in virtual environment HOT 2
- how to set line spacing for shape / tables in pptx?
- BUG: EnsureDispatch always executes the code to build makepy support even if it already exists.
- Error on hosting a FastAPI Application with Windows Service
- `glob.glob1` is deprecated in Python3.13, undocumented and not meant to be public
- Using pydoc on start_pythonwin causes executable code to run
- WM_LBUTTONDOWN not triggered until WM_LBUTTONUP HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pywin32.