Re: How to determine if archive is an sdist or bdist

--===============1324464751==
Content-Type: multipart/alternative; boundary=bcaec543072ad42b4104d942a58a

--bcaec543072ad42b4104d942a58a
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Apr 1, 2013 at 8:13 AM, James Carpenter <[email protected]> wrote:

> Do you have a module/function/line number in easy_install I should use?
> I'm sure I can dig it out myself but it sounds like you might just be able
> to put your finger on it in only a minute or two.
>
> Same question for a pre-existing utility function for reading a
> requirements file. I'm guessing there is one burried down in the PIP code,
> but I haven't looked yet.
>
> A third more interesting question, is whether there is any way to
> determine the origin of an installed package. I am building up a build-info
> to push into Artifactory and it takes a "type" if available when listing
> dependencies of a build. In Java/Maven land a typical type would be jar,
> war, pom, etc. My current understanding is this is a non-sense question,
> since once a Python module is installed it looks the same regardless of
> whether it came from an sdist, wheel, etc.
>

The closest equivalent is PEP 376's "INSTALLER" file, but that only tells
you which installer was used to add the distribution, rather than where
that installer retrieved it from. An "ORIGIN" entry in the installation
database could be an interesting future addition.

Cheers,
Nick.

-- 
Nick Coghlan   |   [email protected]   |   Brisbane, Australia

--bcaec543072ad42b4104d942a58a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Mon, Apr 1, 2013 at 8:13 AM, James Carpenter <span dir=3D"ltr">&=
lt;<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]=
</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Do you have a module/functi=
on/line number in easy_install I should use? I&#39;m sure I can dig it out =
myself but it sounds like you might just be able to put your finger on it i=
n only a minute or two.<div>
<br>
</div><div>Same question for a pre-existing utility function for reading a =
requirements file. I&#39;m guessing there is one burried down in the PIP co=
de, but I haven&#39;t looked yet.</div><div><br></div><div>A third more int=
eresting question, is whether there is any way to determine the origin of a=
n installed package. I am building up a build-info to push into Artifactory=
 and it takes a &quot;type&quot; if available when listing dependencies of =
a build. In Java/Maven land a typical type would be jar, war, pom, etc. My =
current understanding is this is a non-sense question, since once a Python =
module is installed it looks the same regardless of whether it came from an=
 sdist, wheel, etc.</div>
</div></blockquote><div><br></div><div>The closest equivalent is PEP 376&#3=
9;s &quot;INSTALLER&quot; file, but that only tells you which installer was=
 used to add the distribution, rather than where that installer retrieved i=
t from. An &quot;ORIGIN&quot; entry in the installation database could be a=
n interesting future addition.<br>
<br></div><div>Cheers,<br>Nick.<br></div></div><br>-- <br>Nick Coghlan=A0=
=A0 |=A0=A0 <a href=3D"mailto:[email protected]">[email protected]</a>=A0=
=A0 |=A0=A0 Brisbane, Australia
</div></div>

--bcaec543072ad42b4104d942a58a--

--===============1324464751==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Catalog-SIG mailing list
[email protected]
http://mail.python.org/mailman/listinfo/catalog-sig

--===============1324464751==--