Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8609
| From | Hugo Lefeuvre <hle@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Python package providing both modules and an app |
| Date | 2016-06-22 22:00 +0200 |
| Message-ID | <rMWtA-7Ln-15@gated-at.bofh.it> (permalink) |
| References | <rMBfr-2Hb-9@gated-at.bofh.it> <rMF9n-57L-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
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, but python-slugify has been developed as an
application[0] so I think it's rather a bad idea to completely ignore the
entry point, even if it's not really useful. I think upstream would disagree,
too. In my opinion, better build a third package, even if it won't be used
a lot.
> Why not install the command by using the configuration files for
> ‘dh_install(1)’; that is, specify in ‘debian/slugify.install’ the files
> to install.
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). So, I think that what you suggest won't work unless I write my
own entry point, install it via debian/slugify.install and ignore those generated
by setup.py. I think this would be even dirtier than what I already done. ;-)
[0] https://github.com/un33k/python-slugify
--
Hugo Lefeuvre (hle) | www.owl.eu.com
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Python package providing both modules and an app Hugo Lefeuvre <hle@debian.org> - 2016-06-21 23:20 +0200
Re: Python package providing both modules and an app Ben Finney <ben+debian@benfinney.id.au> - 2016-06-22 03:30 +0200
Re: Python package providing both modules and an app Hugo Lefeuvre <hle@debian.org> - 2016-06-22 22:00 +0200
Re: Python package providing both modules and an app Ben Finney <ben+debian@benfinney.id.au> - 2016-06-23 03:10 +0200
Re: Python package providing both modules and an app Hugo Lefeuvre <hle@debian.org> - 2016-06-23 18:40 +0200
Re: Python package providing both modules and an app Hugo Lefeuvre <hle@debian.org> - 2016-06-30 08:30 +0200
Re: Python package providing both modules and an app Thomas Goirand <zigo@debian.org> - 2016-07-05 10:50 +0200
Re: Python package providing both modules and an app Barry Warsaw <barry@debian.org> - 2016-06-23 03:00 +0200
Python program as a command-line program (was: Python package providing both modules and an app) Ben Finney <ben+debian@benfinney.id.au> - 2016-06-23 03:20 +0200
Re: Python program as a command-line program (was: Python package providing both modules and an app) Barry Warsaw <barry@debian.org> - 2016-06-24 21:30 +0200
Re: Python program as a command-line program Ben Finney <ben+debian@benfinney.id.au> - 2016-06-27 09:00 +0200
Re: Python package providing both modules and an app Ian Cordasco <graffatcolmingov@gmail.com> - 2016-06-23 03:30 +0200
Re: Python package providing both modules and an app Thomas Goirand <zigo@debian.org> - 2016-07-05 10:40 +0200
Re: Python package providing both modules and an app Hugo Lefeuvre <hle@debian.org> - 2016-07-05 16:50 +0200
Re: Python package providing both modules and an app Thomas Goirand <zigo@debian.org> - 2016-07-05 21:00 +0200
csiph-web