From: Ralf Dragon <hypnotoad@lindra.de>
To: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] python-sip: fix compile error
Date: Mon, 27 Nov 2023 22:14:29 +0100 [thread overview]
Message-ID: <f0b3caa4-43ce-4f0e-a855-9726f1944644@lindra.de> (raw)
In-Reply-To: <20231125220439.GQ3177259@scaer>
[-- Attachment #1.1: Type: text/plain, Size: 1714 bytes --]
Dear Yann,
thank you for your feedback. As you might have noticed, this is my first
submission to buildroot and I had no contact so far to such a
contribution process. So feedback is appreciated.
> Here, you'd want to explain why it now fails, so that we can assess
> whether we need to backport the fix to maintainance branches.
>
> So, something along the lines of:
>
> siplib: fix build with python >= 3.11
>
> With python 3.11, the PyFrameObject structure members have been
> removed from the public C API:
>
> https://docs.python.org/3.11/whatsnew/3.11.html#whatsnew311-c-api-porting
> https://docs.python.org/3.11/whatsnew/3.11.html#pyframeobject-3-11-hiding
>
> So, use the proper object type that can store an actual
> PyFrameObject.
>
Your description it is already quite good 🙂. I will check again. I have
to say, the patch checker command passed for me, but I was probably in
the long-term branch at that time.
> We also try hard to push patches upstream so that we do not have to
> carry them indefinitely. Please try and submit that patch to the SIP
> project:
> https://riverbankcomputing.com/support/lists
They write that siplib is no longer supported and that 4.19.25 is the
last version: https://riverbankcomputing.com/software/sip/download .
That's why I did not consider asking there.
>> +Index: host-python-sip-4.19.25/siplib/sip.h
>> +===================================================================
> What diff fornat is that? We usually have plain diff, or git-formatted
> patches.
I think it is the output from "git diff" piped into the file.
> Can you look into reworking this patch of yours, please?
Will do.
Best,
Ralf
[-- Attachment #1.2: Type: text/html, Size: 3599 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-11-27 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 17:41 [Buildroot] [PATCH 1/1] python-sip: fix compile error Ralf Dragon
2023-11-25 22:04 ` Yann E. MORIN
2023-11-27 21:14 ` Ralf Dragon [this message]
2023-11-29 6:42 ` Yann E. MORIN
2023-11-29 22:10 ` Ralf Dragon
2023-12-12 15:20 ` Ralf Dragon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f0b3caa4-43ce-4f0e-a855-9726f1944644@lindra.de \
--to=hypnotoad@lindra.de \
--cc=buildroot@buildroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox