Need to support gui_script entry points

[Jim Fulton]

Need to support gui_script entry points :)

[Reinout van Rees (reinout)]

And similarly also the "scripts" entry point.

[Jim Fulton (jim-zope)]

On Tue, Sep 1, 2009 at 10:30 AM, Reinout van Rees<email address hidden> wrote:
> And similarly also the "scripts" entry point.

scripts? wazzat?

Jim

--
Jim Fulton

[Reinout van Rees (reinout)]

Scripts is used by for instance pyflakes and docutils. Here's pyflakes' setup.py:

setup(
    name="pyflakes",
    license="MIT",
    version="0.3.0",
    description="passive checker of Python programs",
    author="Phil Frost",
    maintainer="Moe Aboulkheir",
    <email address hidden>",
    url="http://www.divmod.org/trac/wiki/DivmodPyflakes",
    packages=["pyflakes", "pyflakes.scripts", "pyflakes.test"],
    scripts=["bin/pyflakes"],
    long_description="""Pyflakes is program to analyze Python programs and detect various errors. It
works by parsing the source file, not importing it, so it is safe to use on
modules with side effects. It's also much faster.""")

It is a different way than console_scripts, but with a similar goal. If you add pyflakes or docutils to a zc.recipe.buildout part's eggs list, nothing happens (which is a pain).

So I think this needs implementing (I've already cut a branch to try and get it working, btw).

I see now that gui_scripts is an actual entry point and not a separate option like scripts. I'll file it as a separate bug, then.