public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Neal Gompa <neal@gompa.dev>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
	Victor Stinner <vstinner@redhat.com>,
	Miro Hroncok <mhroncok@redhat.com>,
	David Sterba <dsterba@suse.com>,
	Josef Bacik <josef@toxicpanda.com>
Subject: Re: libbtrfsutil Python bindings FTBFS with Python 3.13 on Fedora Linux 41
Date: Thu, 25 Jul 2024 17:24:25 +0200	[thread overview]
Message-ID: <20240725152425.GA17473@twin.jikos.cz> (raw)
In-Reply-To: <CAEg-Je-tu0DcYvH-mqcv=2xkReYOh9GaeVoJPy0nMD=oqO6stw@mail.gmail.com>

On Sat, Jul 20, 2024 at 12:59:33PM -0400, Neal Gompa wrote:
> Hey all,
> 
> Fedora Linux 41 has upgraded to Python 3.13[1], and as part of it, the
> changes to the interpreter API to remove "private" methods have broken
> the build for python-libbtrfsutil. There's a downstream bug about
> this[2], but the gist of it is that _Py_IDENTIFIER and
> _PyObject_LookupSpecial were removed[3], and so the bindings code
> needs adjustments to fix it.
> 
> Anyone know how to help with this? I'm not really sure how to fix this...
> 
> [1]: https://fedoraproject.org/wiki/Changes/Python3.13
> [2]: https://bugzilla.redhat.com/2245650
> [3]: https://github.com/python/cpython/commit/4fb96a11db5eaca3646bfa697d191469e567d283
> 
> -- 
> 真実はいつも一つ!/ Always, there's only one truth!
> 

Also tracked as https://github.com/kdave/btrfs-progs/issues/838 .

      parent reply	other threads:[~2024-07-25 15:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-20 16:59 libbtrfsutil Python bindings FTBFS with Python 3.13 on Fedora Linux 41 Neal Gompa
2024-07-22 20:23 ` Omar Sandoval
2024-07-25 15:24 ` David Sterba [this message]

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=20240725152425.GA17473@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mhroncok@redhat.com \
    --cc=neal@gompa.dev \
    --cc=vstinner@redhat.com \
    /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