Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

"Implicit conversion changes signedness" warning from unicodeobject.h

Open
#580 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c, java, python
Domain
backend, compilers

Research direction

Start by comparing GraalVM's PyUnicode_KIND declaration with the Python C-API declaration shown in the issue and reproduce the signedness warning. Determine which declaration should match the other, then verify that the warning is resolved without breaking the related Unicode C-API behavior.

Written by the indexing model from the issue text.

Description

good first issue

The GraalVM declares PyUnicode_KIND as

enum PyUnicode_Kind {
/* Return values of the PyUnicode_KIND() function: */
    PyUnicode_1BYTE_KIND = 1,
    PyUnicode_2BYTE_KIND = 2,
    PyUnicode_4BYTE_KIND = 4
};

while Python C-API:

PyAPI_FUNC(int) PyUnicode_KIND(PyObject *op);
Dominant language
Python
Stars
1.6k
Forks
155
Avg merge
8h 58m
Merged PRs (30d)
39

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 oracle/graalpython

All issues in oracle/graalpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.