[Windmill-dev] Hi, and a minor suggestion

[Mikeal Rogers]

> Understood, and what I'm suggesting does not alter this. It just  
> changes (improves, even) how console scripts are created. And this  
> isn't a zc.buildout feature, it's a setuptools feature. Basically,  
> you add to your setup() call:
>
> 	entry_points="""
> 		[console_scripts]
> 		windmill = windmill.bin.windmill_bin:main
> 	"""
>
> And setuptools will automatically generate a script file for you,  
> including a little .exe on Windows. And, in my particular usage,  
> zc.buildout will generate a modified script in the contained install  
> environment's bin directory that explicitly sets all of the eggs on  
> the pythonpath.
>
> The entry point above would replace the scripts line in the setup()  
> call. This feature is documented here:
>
> http://peak.telecommunity.com/DevCenter/setuptools#automatic-script-creation

Ok, we current use the scriptfile option to build/install what is  
essentially a windmill stub script. I know that we've had issues on  
windows with that method, and this sounds like it's much better  
supported.

I would love a patch, if not I'll get to this eventually since it  
sounds like a really good feature.
>
> I'll have to take you up on that some time. Are you going to be at  
> PyCon this year? Might be nice to have a little testing pow-wow.

I was going to go to PyCon but I recently started a new position at  
Mozilla and I don't think I want to take any time away from my new  
work so early on. Hopefully I'll be there next year. I should still be  
attending OSCON if all goes well.

-Mikeal