Add the version bridge for `BYTE` in the `GUID` module.

Open Beginner friendly
#696 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by locating the GUID module and its current BYTE definition, then inspect how the project supports different Python versions. Verify the type on supported versions and consider the requested compatibility behavior done when BYTE resolves to the intended unsigned-byte ctypes type across them.

Written by the indexing model from the issue text.

Description

good first issue

From https://github.com/enthought/comtypes/pull/694#discussion_r1876991821:

To be sure that BYTE is c_ubyte on any python version comtypes support, shouldn't we do this?


if sys.version_info >= (3, 12):

    from ctypes.wintypes import BYTE

else:

    from ctypes import c_ubyte

    BYTE = c_ubyte
Dominant language
Python
Stars
346
Forks
105
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from enthought/comtypes

All issues in enthought/comtypes

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.