On Wed, May 6, 2009 at 10:11 PM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Wed, May 6, 2009 at 9:20 PM, P.J. Eby p...@telecommunity.com wrote:
At 08:58 PM 5/6/2009 +0200, Tarek Ziadé wrote:
Sorry to post again that mail, but it seems that this is the last
remaining
issue for the
There are *many* benefits of adding entry points into Distutils. In
fact, adding a plugin system in there,
will help make the commands more extendable and therefore will help us
in the long term to remove things
out of Distutils.
So any strong opinion against them ?
If not, I'll add a
Hi,
Here's a quick summary of the ongoing work in Distutils, on the issues
we seem to reach a consensus.
The goal would be to finish the discussions on those and to push them
in some kind of Distutils official roadmap
then look at implementation details (for instance, the pkgutil APIs
will be
On Thu, May 7, 2009 at 7:18 AM, P.J. Eby p...@telecommunity.com wrote:
At 08:28 PM 5/6/2009 +0200, Hanno Schlichting wrote:
Doug Hellmann wrote:
On May 6, 2009, at 1:46 PM, P.J. Eby wrote:
At 10:59 AM 5/6/2009 -0400, Doug Hellmann wrote:
On May 5, 2009, at 10:50 PM, P.J. Eby wrote:
On May 6, 2009, at 9:38 PM, Wheat wrote:
I'll also mention my most common use-case for using entry_points is
installing
console_scripts using zc.recipe.egg.
I'm curious about that because I've never understood the benefit of
using entry points for console scripts. Why not just list the
2009/5/7 Doug Hellmann doug.hellm...@gmail.com:
I would argue the other way. Why force authors of console scripts to deal
with entry points instead of just installing the script as-is?
Please explain as-is with reference to ensuring that the script
works cross-platform. I think the benefit of
On May 7, 2009, at 8:54 AM, Paul Moore wrote:
2009/5/7 Doug Hellmann doug.hellm...@gmail.com:
I would argue the other way. Why force authors of console scripts
to deal
with entry points instead of just installing the script as-is?
Please explain as-is with reference to ensuring that the
2009/5/7 Doug Hellmann doug.hellm...@gmail.com:
I write a python script call hello.py like this:
#!/usr/bin/env python
def main():
print 'hello!'
if __name__ == '__main__':
main()
Why make me define an entry point for that? I can just
On Thu, May 07, 2009 at 03:03:29PM +0100, Paul Moore wrote:
2009/5/7 Doug Hellmann doug.hellm...@gmail.com:
Why make me define an entry point for that? I can just put it in /usr/bin
or somewhere in the path on Windows and call it as hello.py.
That works but a lot of Unix users have in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Smith wrote:
Doug Hellmann wrote:
On May 7, 2009, at 8:54 AM, Paul Moore wrote:
2009/5/7 Doug Hellmann doug.hellm...@gmail.com:
I would argue the other way. Why force authors of console scripts to
deal
with entry points instead of just
On May 7, 2009, at 10:03 AM, Paul Moore wrote:
2009/5/7 Doug Hellmann doug.hellm...@gmail.com:
Does setuptools give me something extra for Windows? I'm not a
regular
Windows user, so it's likely that there are features I don't know
about.
I don't think so, as such. It gives Unix and
2009/5/7 Tres Seaver tsea...@palladion.com:
Eric Smith wrote:
Doug Hellmann wrote:
On May 7, 2009, at 8:54 AM, Paul Moore wrote:
2009/5/7 Doug Hellmann doug.hellm...@gmail.com:
I would argue the other way. Why force authors of console scripts to
deal
with entry points instead of just
On May 7, 2009, at 10:20 AM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Smith wrote:
Doug Hellmann wrote:
On May 7, 2009, at 8:54 AM, Paul Moore wrote:
2009/5/7 Doug Hellmann doug.hellm...@gmail.com:
I would argue the other way. Why force authors of console
I write a python script call hello.py like this:
#!/usr/bin/env python
def main():
print 'hello!'
if __name__ == '__main__':
main()
Why make me define an entry point for that? I can just put it in /usr/
bin or somewhere in the
Doug Hellmann doug.hellm...@gmail.com writes:
I write a python script call hello.py like this:
#!/usr/bin/env python
def main():
print 'hello!'
if __name__ == '__main__':
main()
Why make me define an entry point for that? I can just
Paul Moore wrote:
2009/5/7 Tres Seaver tsea...@palladion.com:
Eric Smith wrote:
Yes. It creates a .exe wrapper [1]. By using entry points, I don't need
to care what the target system is. Also, /usr/bin/env might invoke the
wrong python.
Exactly: using entry points for console scripts
On Fri, May 8, 2009 at 10:04 AM, Eric Smith e...@trueblade.com wrote:
Paul Moore wrote:
2009/5/7 Tres Seaver tsea...@palladion.com:
Eric Smith wrote:
Yes. It creates a .exe wrapper [1]. By using entry points, I don't need
to care what the target system is. Also, /usr/bin/env might invoke
On May 6, 12:07 am, Andreas Jung li...@zopyx.com wrote:
On 28.04.09 14:58, Andreas Jung wrote:
On 28.04.2009 14:51 Uhr, Chris Withers wrote:
Andreas Jung wrote:
it is known that the latest setuptools version produces broken
packages with SVN 1.6 checkouts. Could we get a fixed
On May 7, 2009, at 5:53 PM, Ben Finney wrote:
Doug Hellmann doug.hellm...@gmail.com writes:
I write a python script call hello.py like this:
#!/usr/bin/env python
def main():
print 'hello!'
if __name__ == '__main__':
main()
Why make
At 10:21 AM 5/8/2009 +1200, Noah Gift wrote:
1. Different versions of Python conflict with previous versions of
console scripts. Take paste for example.
I don't understand what you mean.
2. The entry point mechanism IIRC recursively scans the site-packages
directory and loads up the
resending, as I accidently only sent to PJE
On Fri, May 8, 2009 at 11:48 AM, Noah Gift noah.g...@gmail.com wrote:
On Fri, May 8, 2009 at 11:24 AM, P.J. Eby p...@telecommunity.com wrote:
At 10:21 AM 5/8/2009 +1200, Noah Gift wrote:
1. Different versions of Python conflict with previous
At 10:38 AM 5/7/2009 -0400, Doug Hellmann wrote:
pip installs my scripts into a virtualenv without any issue and
without using entry points, AFAICT.
I guess if we move to requiring entry points and disallowing simple
script distribution I'll need to find another way to package
On May 7, 2009, at 7:28 PM, P.J. Eby wrote:
At 10:38 AM 5/7/2009 -0400, Doug Hellmann wrote:
pip installs my scripts into a virtualenv without any issue and
without using entry points, AFAICT.
I guess if we move to requiring entry points and disallowing simple
script distribution I'll need
At 01:14 PM 5/7/2009 -0700, Wheat wrote:
But then having both 'scripts' and 'entry_points/console_scripts' is
less than perfect since it introduces (mostly) unneccessary TIMTOWTDI.
I interpret 'scripts' as meaning non-Python scripts, so there is
still only one obvious way to do each thing.
Paul Moore wrote:
That works but a lot of Unix users have in the past objected to having
'.py' in the name.
So install a symlink from hello - hello.py.
--
Greg
___
Distutils-SIG maillist - Distutils-SIG@python.org
25 matches
Mail list logo
