On Aug 31, 2009, at 7:52 AM, Chris Withers wrote:
Jim Fulton wrote:
On Wed, Aug 26, 2009 at 2:12 PM, Chris
Withers<[email protected]> wrote:
Jim Fulton wrote:
http://docs.python.org/library/runpy.html#module-runpy
Hmmm, maybe it does just the right thing for -m?
Perhaps.
In any case, any objections to me implementing this for buildout
scripts?
No, but I want to review it before you merge it to trunk.
If not, where is the actual code that generates the scripts?
In the easy_install meodule.
Okay, I'll add it to my to-do list...
...don't worry, no risk of it getting to the top anytime soon ;-)
I went ahead and implemented this in 1.4.1.
Exellent, thanks :-)
...although I think there may still be some rough edges:
bin/py -m somemodule --some --options
...will throw an exception as the code in py tries to consume all
the parameters.
"real" python only consumes the -m and passed the rest on to the
script.
The same is true for -c, which we've had for awhile and has the same
rough edge. (I changed that in a hacky way for my branch for -c, and
now for -m. I'll be trying to change that to use optparse very soon,
though someone may beat me to it.)
Gary
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
