From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-python@lists.gentoo.org
Subject: [gentoo-python] What are the issues with Python namespaces?
Date: Fri, 4 Jan 2013 00:26:02 +0100 [thread overview]
Message-ID: <20130104002602.57a47d0e@pomiocik.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
Hi,
Arfrever likes to talk much about Python namespaces not being supported
by Gentoo but I feel like he's the only one knowing what the problems
exactly are. So, can you, Arfrever, or anyone else explain me what
exact problems we have to handle?
So far I was able to guess that it's about __init__.py files being
installed in parent directories of packages installed via namespaces.
I'd guess the major issue then is that if two packages install modules
like foo/A and foo/B, then both would try to install foo/__init__.py,
colliding painfully. And that seems to be the major thing addressed
by Progress namespaces support.
Looking at my tiny number of Python packages installed with namespaces,
I see two cases:
1) zope-fixers and zope-interface -- both install to 'zope', none
installs '__init__.py',
2) logilab-common -- installs to 'logilab' with other logilab packages,
and installs '__init__.py' there.
Is that something semi-random or does that mean that some upstreams
actually handle namespaces themselves?
I guess namespaces also like to cause trouble with tests and PYTHONPATH.
Am I misunderstand it? Missing something?
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
reply other threads:[~2013-01-03 23:26 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=20130104002602.57a47d0e@pomiocik.lan \
--to=mgorny@gentoo.org \
--cc=gentoo-python@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