On Sun, Mar 31, 2013 at 6:13 PM, James Carpenter 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.
It's the install_eggs() method of
setu
On Mon, Apr 1, 2013 at 8:13 AM, James Carpenter 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 ut
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
On Fri, Mar 29, 2013 at 11:00 AM, James Carpenter wrote:
> Looks like the idea of using a custom command is a better approach then.
I'm not sure why you think that. The only kinds of archives whose
file types are ambiguous from the name, are sdist, bdist_dumb, and
random raw source dumps. Every
On Thu, Mar 28, 2013 at 3:57 PM, James Carpenter wrote:
> Is there an easy way to programmatically tell if an archive (tar.gz, zip,
> etc.) in the dist directory is a binary or sdist? I would like to
> post-process the contents of a dist directory and classify each build
> artifact there (egg, sdi
Is there an easy way to programmatically tell if an archive (tar.gz, zip,
etc.) in the dist directory is a binary or sdist? I would like to
post-process the contents of a dist directory and classify each build
artifact there (egg, sdist, bdist, etc.).
Currently the only approach I know of is to ha
