Hi,
On Mon, Nov 11, 2013 at 8:45 PM, Barry Warsaw wrote:
> Am I missing anything? Can anybody improve on those rules above? Should we
> just adopt them as our standard recommendation (not requirement)?
I would also add this:
* Do not use version-specific scripts unless there is real need for
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
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
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
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
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
6 matches
Mail list logo
