public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steven Sun <StevenSun2021@hotmail.com>
To: Eric Feng <ef2648@columbia.edu>
Cc: David Malcolm <dmalcolm@redhat.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Query status of GSoC project: CPyChecker
Date: Thu, 29 Jun 2023 07:40:57 +0000	[thread overview]
Message-ID: <TYAP286MB05219F01E7007C04FCB775E6B925A@TYAP286MB0521.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CANGHATV+g4ncZo6RXOfrw6Y=+0xu3Vn8Nu03uP4kgPqNa0WAuA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]

Hi Eric,

> Thanks for reaching out. The project is still in very early stages. So
> far we have taught the analyzer the basic behavior for
> PyLong_FromLong, PyList_New, and Py_DECREF via known function
> subclassing. Additionally, Py_INCREF is supported out of the box.
> Reference count checking functionality remains the priority, but it is
> not yet fully implemented.

Great!

> Regarding CPython versions, the goal is to just get things working on
> one version first. I arbitrarily picked 3.9, but happy to consider
> another version as an initial goal if it’s more helpful to the CPython
> community.

I am not sure about this.

cpychecker is more beneficial to CPython extension devs than to
CPython devs, since it is almost impossible to let the cpychecker learn
the most updated internal function definitions without handwritten
attributes or seeing the whole function definitions.

So it depends on the extension maintainer. I am observing this pattern
that popular libraries are gradually upgrading. 3.9 and 3.10 is definitely
the current mainstream.

Saying so, I think 3.9 is fine for now, but it will be outdated after 2 to 3
years.


Best,
Steven

      reply	other threads:[~2023-06-29  7:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 10:03 Steven Sun
2023-06-28 22:09 ` Eric Feng
2023-06-29  7:40   ` Steven Sun [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=TYAP286MB05219F01E7007C04FCB775E6B925A@TYAP286MB0521.JPNP286.PROD.OUTLOOK.COM \
    --to=stevensun2021@hotmail.com \
    --cc=dmalcolm@redhat.com \
    --cc=ef2648@columbia.edu \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).