Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.freenet.ag!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Newsgroups: comp.lang.python
Date: Tue, 26 Mar 2013 11:41:57 -0700 (PDT)
In-Reply-To: <mailman.3754.1364315646.2939.python-list@python.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=71.183.236.17; posting-account=jKjGDQoAAABKN2iauJtD3DV5oMZpXuQo
References: <mailman.3685.1364166787.2939.python-list@python.org> <514f9a0b$0$30001$c3e8da3$5496439d@news.astraweb.com> <0f669e21-5fd1-402e-9d96-55aa647d1030@googlegroups.com> <mailman.3754.1364315646.2939.python-list@python.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Subject: Re: import in Python3.3
From: rocky <rocky@gnu.org>
To: comp.lang.python@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: python-list@python.org
Precedence: list
Message-ID: <mailman.3766.1364323326.2939.python-list@python.org>
Lines: 52
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:41937

On Tuesday, March 26, 2013 12:33:54 PM UTC-4, Jerry Hill wrote:
> On Mon, Mar 25, 2013 at 11:49 PM, rocky wrote:
>=20
> >> On Sun, 24 Mar 2013 18:12:49 -0500, Fabian von Romberg wrote:
>=20
> >> > I have a package name collections and inside of my package I want to
>=20
>=20
>=20
> > I find this kind of thing sad: it feels to me that programmers are work=
ing around somewhat arbitrary and changing restrictions. Rather than avoid =
names like "collections", why not try to address the underlying problem? Th=
ere isn't an ambiguity here in my view: the fullname is mypackage.collectio=
ns
>=20
>=20
>=20
> You've said a couple of times now that the original author has a
>=20
> package named "mypackage" with a module "collections" in it.  As far
>=20
> as I can tell, that's untrue.  The original post claims to have a
>=20
> package named "collections", which is colliding with the builtin
>=20
> module of the same name.
>=20
>=20
>=20
> As far as I can tell, all of your suggestions about using your
>=20
> pyimport-relative tool aren't helpful unless the author re-names his
>=20
> package from "collections" to "mypackage" and then moves all of their
>=20
> code into a "collections" module inside "mypackage", right?

Right. Perhaps then I misunderstand. Having a package called "collections" =
when there is something out there already called "collections" clearly ill =
advised.=20

But in that case, using sys.path to get around this is still a bad idea: th=
e clash should be fixed. Sure, only in the case that this really can't be a=
ddressed would I use sys.path.

>=20
>=20
>=20
> --=20
>=20
> Jerry