public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] install-qa-check.d: Add namespace package check to 60python-site
Date: Thu, 29 May 2025 08:51:11 +0200	[thread overview]
Message-ID: <c534d9f8dbacac2f9d07903eab67b5c809004f46.camel@gentoo.org> (raw)
In-Reply-To: <3618cf7b-c4da-4bb2-a480-dfb2de889f0c@gentoo.org>

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

On Thu, 2025-05-29 at 02:41 -0400, Eli Schwartz wrote:
> > The eclass handled the most common
> > case of installing them via the deprecated `namespace_packages`
> > setuptools key, but it does not handle packages that worked around
> > the deprecation warning by installing the file manually.
> 
> 
> Projects don't always "install the file manually". Sometimes they have
> code which needs to run in __init__.py but *also* need to expose the
> namespace to other code.
> 

Do you have a single valid use case in ::gentoo?  I.e. a package that
actually:

1) installs a top-level __init__.py with namespace support and other
code,

2) actually has subpackages that would require namespace support.

Because I dare say catching them is better than ignoring them
and waiting for the file collisions because of a potentially valid use
case that wouldn't be relevant to Gentoo installs anyway.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]

      reply	other threads:[~2025-05-29  6:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29  6:16 [gentoo-dev] [PATCH] install-qa-check.d: Add namespace package check to 60python-site Michał Górny
2025-05-29  6:41 ` Eli Schwartz
2025-05-29  6:51   ` Michał Górny [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=c534d9f8dbacac2f9d07903eab67b5c809004f46.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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