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

Fix: win32print.SetJob sending ANSI to UNICODE API #1849

Merged
merged 2 commits into from Mar 30, 2022

Conversation

CristiFati
Copy link
Contributor

@CristiFati CristiFati commented Mar 30, 2022

Fix for #1281.

Confirmed when investigating [SO]: How to change username of job in print queue using python & win32print.

Modified the script in the bug. The scenario is even easier to reproduce: simply pass the dictionary returned by GetJob to SetJob, and the error pops up (actually there are different errors depending on level (1, 2) - as also encountered in the SO URL).

The cause is straightforward: JOB_INFO_* structures have LPTSTR (wchar_t* when built with -DUNICODE -D_UNICODE) members, while PyArg_ParseTupleAndKeywords, fills char* s for z format specifiers. Check [Python.Docs]: Parsing arguments and building values.

The fix is to specify the Unicode format specifier (Z).

After rebuilding the .pyd (and placing it in the site-packages dir), the error no longer pops up, and changing existing jobs string properties is possible (tried setting pUserName to random strings and the change is reflected in the print queue).

Environment: Python 3.9.9 (pc064) with PyWin32 303.

@mhammond
Copy link
Owner

That looks great, thanks! Do you mind adding an entry to CHANGES.txt with a mention of #1281 and crediting yourself however you like?

@CristiFati
Copy link
Contributor Author

CristiFati commented Mar 30, 2022

@mhammond: Done. Hmmm I wonder if it would be possible for CHANGES.txt (and most likely other files) to be excluded from CI workflows (partially possible with https://docs.github.com/en/actions/managing-workflow-runs/skipping-workflow-runs).

@mhammond
Copy link
Owner

Thank you!

I wonder if it would be possible for CHANGES.txt (and most likely other files) to be excluded from CI workflows (partially possible with https://docs.github.com/en/actions/managing-workflow-runs/skipping-workflow-runs).

Possibly, but it's quite rare that this happens, so my motivation is low - I'd welcome PRs etc though :)

@mhammond mhammond merged commit 7dca967 into mhammond:main Mar 30, 2022
@CristiFati CristiFati deleted the cfati_dev0 branch April 10, 2022 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants