Re: CLI recommendations for version-specific /usr/bin scripts

2013-11-11 Thread Barry Warsaw
On Nov 12, 2013, at 10:09 AM, Ben Finney wrote: >Barry Warsaw writes: > >> Some cli's do care though, e.g. nose. In those cases, I think common >> practice seems to be the following: > >> […] >> * Expose /usr/bin/foo with a shebang line of #!/usr/bin/python >> >> * Expose /usr/bin/foo-3 with a

Re: CLI recommendations for version-specific /usr/bin scripts

2013-11-11 Thread Barry Warsaw
On Nov 11, 2013, at 10:13 AM, Thomas Kluyver wrote: >On 11 November 2013 08:45, Barry Warsaw wrote: > >> * Expose /usr/bin/foo with a shebang line of #!/usr/bin/python >> >> * Expose /usr/bin/foo-3 with a shebang line of #!/usr/bin/python3 >> > >In upstream IPython, we now install an ipython2 s

Re: CLI recommendations for version-specific /usr/bin scripts

2013-11-11 Thread Ben Finney
Barry Warsaw writes: > Some cli's do care though, e.g. nose. In those cases, I think common > practice seems to be the following: > […] > * Expose /usr/bin/foo with a shebang line of #!/usr/bin/python > > * Expose /usr/bin/foo-3 with a shebang line of #!/usr/bin/python3 In cases where the com

Re: CLI recommendations for version-specific /usr/bin scripts

2013-11-11 Thread Zygmunt Krynicki
Hi Barry, Thomas. On Mon, Nov 11, 2013 at 7:13 PM, Thomas Kluyver wrote: > On 11 November 2013 08:45, Barry Warsaw wrote: > >> > Question: dash or no dash in the script name? >> > I personally like the name-version format as it often separates things in Debian so I'd tab-tab until I get to see s

Re: CLI recommendations for version-specific /usr/bin scripts

2013-11-11 Thread Thomas Kluyver
On 11 November 2013 08:45, Barry Warsaw wrote: > * Expose /usr/bin/foo with a shebang line of #!/usr/bin/python > > * Expose /usr/bin/foo-3 with a shebang line of #!/usr/bin/python3 > In upstream IPython, we now install an ipython2 script on Python 2, paralleling the ipython3 script. The packa

CLI recommendations for version-specific /usr/bin scripts

2013-11-11 Thread Barry Warsaw
I'd like to revive the discussion on best practices for installing Python applications which are version-dependent. If we can come up with some general guidelines we can mostly agree on, I'll update the AppStyleGuide wiki page. Of course, most Python applications which expose a cli don't need to

Re: Simplified library style guide based on pybuild

2013-11-11 Thread Barry Warsaw
On Nov 11, 2013, at 09:34 AM, Piotr Ożarowski wrote: >it should match module name, not source package name (which doesn't >match module name in most cases). Thanks for fixing the wiki! -Barry -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Tr

Re: Simplified library style guide based on pybuild

2013-11-11 Thread Piotr Ożarowski
[Steve Langasek, 2013-11-11] > A few questions: > > (On PYBUILD_NAME) > Here, we're telling it that the name is foo. This should match the source > package name, so for example, in enum34, you'd see: [...] > > If it's supposed to match the source package name, why does it need to be > speci