Need to support gui_script entry points

Bug #116437 reported by Jim Fulton on 2007-05-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Need to support gui_script entry points :)

Jim Fulton (jim-zope) on 2007-05-31
Changed in zc.buildout:
status: Unconfirmed → Confirmed
importance: Undecided → High
Reinout van Rees (reinout) wrote :

And similarly also the "scripts" entry point.

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 Fulton

Reinout van Rees (reinout) wrote :

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

    description="passive checker of Python programs",
    author="Phil Frost",
    maintainer="Moe Aboulkheir",
    <email address hidden>",
    packages=["pyflakes", "pyflakes.scripts", "pyflakes.test"],
    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.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers