Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #13436 > unrolled thread
| Started by | Nicholas D Steeves <sten@debian.org> |
|---|---|
| First post | 2021-06-25 22:50 +0200 |
| Last post | 2021-06-28 18:30 +0200 |
| Articles | 2 on this page of 22 — 10 participants |
Back to article view | Back to linux.debian.maint.python
[RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Nicholas D Steeves <sten@debian.org> - 2021-06-25 22:50 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Jeremy Stanley <fungi@yuggoth.org> - 2021-06-25 23:20 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Scott Talbert <swt@techie.net> - 2021-06-25 23:40 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Nicholas D Steeves <sten@debian.org> - 2021-06-26 00:50 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Nicholas D Steeves <sten@debian.org> - 2021-06-26 00:30 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Jeremy Stanley <fungi@yuggoth.org> - 2021-06-26 01:50 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Nicholas D Steeves <sten@debian.org> - 2021-06-26 02:10 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Paul Wise <pabs@debian.org> - 2021-06-26 04:10 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Jeremy Stanley <fungi@yuggoth.org> - 2021-06-26 06:20 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Martin <debacle@debian.org> - 2021-06-26 11:30 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Simon McVittie <smcv@debian.org> - 2021-06-26 12:20 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Paul Wise <pabs@debian.org> - 2021-06-26 04:00 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Simon McVittie <smcv@debian.org> - 2021-06-26 00:10 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Nicholas D Steeves <sten@debian.org> - 2021-06-26 01:10 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Jeremy Stanley <fungi@yuggoth.org> - 2021-06-26 02:00 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Brian Thompson <brian@hashvault.io> - 2021-06-26 05:50 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Donald Stufft <donald@stufft.io> - 2021-06-26 06:30 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Paul Wise <pabs@debian.org> - 2021-06-26 04:00 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Louis-Philippe Véronneau <pollo@debian.org> - 2021-06-27 01:00 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Jeremy Stanley <fungi@yuggoth.org> - 2021-06-27 02:20 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Emmanuel Arias <eamanu@yaerobi.com> - 2021-06-28 04:50 +0200
Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs Jeremy Stanley <fungi@yuggoth.org> - 2021-06-28 18:30 +0200
Page 2 of 2 — ← Prev page 1 [2]
| From | Emmanuel Arias <eamanu@yaerobi.com> |
|---|---|
| Date | 2021-06-28 04:50 +0200 |
| Message-ID | <CuPvs-34b-1@gated-at.bofh.it> |
| In reply to | #13454 |
[Multipart message — attachments visible in raw view] — view raw
Hola everybody, On 6/26/21 7:51 PM, Louis-Philippe Véronneau wrote: > To me, the most important thing is that all packages must at least run > the upstream testsuite when it exists (I'm planning on writing a policy > proposal saying this after the freeze). If PyPi releases include them, I > think it's fine (but they often don't). I was a little surprised because in all discussion anyone take account the tests (or if a missed sorry) thanks pollo to get it in discussion. I don't have the correct numbers but I saw many python package without autopkgtest, and if we package from PyPi, that don't contain the testsuite, that result in packages with any test, and that isn't good. Also, I'm not sure, but the docs aren't in PyPi, isn't? In the other hand, files like .git* or CI files, can be easily remove it. So, I don't see any problems with that. cheers -- Emmanuel Arias @eamanu yaerobi.com
[toc] | [prev] | [next] | [standalone]
| From | Jeremy Stanley <fungi@yuggoth.org> |
|---|---|
| Date | 2021-06-28 18:30 +0200 |
| Message-ID | <Cv2j0-2Dr-3@gated-at.bofh.it> |
| In reply to | #13456 |
[Multipart message — attachments visible in raw view] — view raw
On 2021-06-27 23:49:18 -0300 (-0300), Emmanuel Arias wrote: [...] > if we package from PyPi, that don't contain the testsuite, that > result in packages with any test, and that isn't good. > > Also, I'm not sure, but the docs aren't in PyPi, isn't? [...] This depends entirely on how upstream is creating their sdists. They might certainly choose to omit tests or even documentation, but I think that's becoming less popular now that wheels exist. It is expected for a wheel to omit basically everything except the application, licensing information and some metadata. This has reduced the pressure on upstreams with massive suites of tests or volumes of documentation to strip them out of sdists, making it more likely they'll ship full source distributions that way. -- Jeremy Stanley
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | linux.debian.maint.python
csiph-web