On Jun 22, 2016 7:54 PM, "Barry Warsaw" wrote:
>
> On Jun 22, 2016, at 11:25 AM, Ben Finney wrote:
>
> >This seems to be more common now that command-line invocation is
> >becoming even more discouraged. When the upstream documentation
> >recommends ‘python3 -m foo.bar’ as the primary means of inv
Barry Warsaw writes:
> On Jun 22, 2016, at 11:25 AM, Ben Finney wrote:
>
> >There is a compounding tendency to disparage ‘python3 ./foo/bar.py’,
> >[…]. I wish this trend could be effectively reversed, because IMO
> >this is a serious impediment to considering Python a good choice for
> >command-
Hugo Lefeuvre writes:
> The entry point is generated by 'setup.py install_scripts', which is
> executed by pybuild after files specified in *.install have been
> installed (correct me if I'm wrong).
I haven't demonstrated for this case, but I would be surprised if that's
how it behaves. To my mi
On Jun 22, 2016, at 11:25 AM, Ben Finney wrote:
>This seems to be more common now that command-line invocation is
>becoming even more discouraged. When the upstream documentation
>recommends ‘python3 -m foo.bar’ as the primary means of invoking the
>command line functionality, that really blurs th
Hi Ben,
> > The package is originally requested as a Python module[2] and it seems
> > clear to me that the whole thing is only useful as a library
>
> I don't understand this statement. If it is *only* useful as a library,
> why install the command-line entry point?
Indeed, I though about that
[Iain R. Learmonth, 2016-06-22]
> * Package name: python-pytz
> Version : 2016.4
> Upstream Author : Stuart Bishop
> * URL : http://pythonhosted.org/pytz
> * License : MIT
> Programming Lang: Python
> Description : World timezone definitions, modern and h
6 matches
Mail list logo
