DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1348] Add a procedure for updating required Python version
Date: Wed, 10 Jan 2024 09:18:25 +0000	[thread overview]
Message-ID: <bug-1348-3@http.bugs.dpdk.org/> (raw)

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

https://bugs.dpdk.org/show_bug.cgi?id=1348

            Bug ID: 1348
           Summary: Add a procedure for updating required Python version
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: dts
          Assignee: dev@dpdk.org
          Reporter: juraj.linkes@pantheon.tech
                CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
  Target Milestone: ---

The first question is do we ever want to update the required Python version?

If so, then we need to agree on what the (possible) criteria are. The actual
decision is likely to be a judgment call after looking over the criteria.

The current reasons to update are:
3.11 has StrEnum. We have our own implementation of StrEnum, so this would be a
nice to have.
3.11 also has @typing.overload, which would be useful for Node factory
functions (SutConfig|TGConfig -> SutNode|TGNode). Provided by
typing_extensions, changed in 4.2.0.
3.12 has @typing.override (useful for docs), but we can get that with the
typing_extensions module (version 4.4.0, but changed in 4.5.0). Tt doesn't work
with Pylama though due to a bug: https://github.com/klen/pylama/pull/247, but
that is not a big deal since we should move away from Pylama since it's not
maintained anymore (or seems not to be).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3535 bytes --]

                 reply	other threads:[~2024-01-10  9:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-1348-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.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 NNTP newsgroup(s).