Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #10173 > unrolled thread
| Started by | Julien Puydt <julien.puydt@laposte.net> |
|---|---|
| First post | 2018-02-15 16:10 +0100 |
| Last post | 2018-02-21 10:40 +0100 |
| Articles | 5 — 3 participants |
Back to article view | Back to linux.debian.maint.python
Thread on flit... Julien Puydt <julien.puydt@laposte.net> - 2018-02-15 16:10 +0100
Re: Thread on flit... Paul Wise <pabs@debian.org> - 2018-02-17 08:00 +0100
Re: Thread on flit... Julien Puydt <julien.puydt@laposte.net> - 2018-02-17 09:50 +0100
Re: Thread on flit... Paul Wise <pabs@debian.org> - 2018-02-17 12:10 +0100
Re: Thread on flit... Robert Collins <robertc@robertcollins.net> - 2018-02-21 10:40 +0100
| From | Julien Puydt <julien.puydt@laposte.net> |
|---|---|
| Date | 2018-02-15 16:10 +0100 |
| Subject | Thread on flit... |
| Message-ID | <vjtkD-4n0-21@gated-at.bofh.it> |
Hi, a new building/packaging/publishing/whatevering tool for Python modules has appeared sometime ago : flit. The homepage is here : https://github.com/takluyver/flit I know a few packages using it already ; and I have terminado (from the same author as flit) which I would like to update. It might be needing a team-level discussion, so I'm opening a thread here : should support for it be added to our current package building tools? Should it be packaged? Snark on #debian-python
[toc] | [next] | [standalone]
| From | Paul Wise <pabs@debian.org> |
|---|---|
| Date | 2018-02-17 08:00 +0100 |
| Message-ID | <vk4Dv-3lC-1@gated-at.bofh.it> |
| In reply to | #10173 |
On Thu, Feb 15, 2018 at 11:05 PM, Julien Puydt wrote: > Should it be packaged? If it meets Debian standards and is needed by another package, there is no reason why it shouldn't be packaged. -- bye, pabs https://wiki.debian.org/PaulWise
[toc] | [prev] | [next] | [standalone]
| From | Julien Puydt <julien.puydt@laposte.net> |
|---|---|
| Date | 2018-02-17 09:50 +0100 |
| Message-ID | <vk6lX-4xT-3@gated-at.bofh.it> |
| In reply to | #10175 |
Hi, Le 17/02/2018 à 07:59, Paul Wise a écrit : > On Thu, Feb 15, 2018 at 11:05 PM, Julien Puydt wrote: > >> Should it be packaged? > > If it meets Debian standards and is needed by another package, there > is no reason why it shouldn't be packaged. > It is intended for trivial packaging... so perhaps dh_python could detect its use and do something smarter. Snark on #debian-python
[toc] | [prev] | [next] | [standalone]
| From | Paul Wise <pabs@debian.org> |
|---|---|
| Date | 2018-02-17 12:10 +0100 |
| Message-ID | <vk8xr-6eS-5@gated-at.bofh.it> |
| In reply to | #10176 |
On Sat, Feb 17, 2018 at 4:41 PM, Julien Puydt wrote: > It is intended for trivial packaging... so perhaps dh_python could > detect its use and do something smarter. Ideally, debhelper should DTRT no matter what build system is in use. -- bye, pabs https://wiki.debian.org/PaulWise
[toc] | [prev] | [next] | [standalone]
| From | Robert Collins <robertc@robertcollins.net> |
|---|---|
| Date | 2018-02-21 10:40 +0100 |
| Message-ID | <vlz2y-50Q-15@gated-at.bofh.it> |
| In reply to | #10177 |
On 18 February 2018 at 00:03, Paul Wise <pabs@debian.org> wrote: > On Sat, Feb 17, 2018 at 4:41 PM, Julien Puydt wrote: > >> It is intended for trivial packaging... so perhaps dh_python could >> detect its use and do something smarter. > > Ideally, debhelper should DTRT no matter what build system is in use. Agreed. Its worth noting though that we've finally introduced a build system abstraction into Python, so dh_python should instead learn to drive PEP-517 build systems; that will support flit and others over time. It does require a python thunk, sadly - see PEP 516 which was the alternative :) - but its not too deep an issue to write that and slap a CLI on it for dh_python to use. -Rob
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web