Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #10032 > unrolled thread
| Started by | Guðjón Guðjónsson <gudjon.i.gudjonsson@gmail.com> |
|---|---|
| First post | 2018-01-10 21:30 +0100 |
| Last post | 2018-01-13 09:10 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.maint.python
PyQwt3D packaging strategy Guðjón Guðjónsson <gudjon.i.gudjonsson@gmail.com> - 2018-01-10 21:30 +0100
Re: PyQwt3D packaging strategy Dmitry Shachnev <mitya57@debian.org> - 2018-01-13 09:10 +0100
| From | Guðjón Guðjónsson <gudjon.i.gudjonsson@gmail.com> |
|---|---|
| Date | 2018-01-10 21:30 +0100 |
| Subject | PyQwt3D packaging strategy |
| Message-ID | <v6vax-7d1-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hi list I am updating my package pyqwt3d. It is tested for Qt5, python2 and python3. The changes were so huge that I made GitHub fork of it: https://github.com/GauiStori/PyQwt3D Now I have two questions: 1. Shall I skip the python2 version since it is already end of life? 2. Shall I make my changes into a huge patch (changes from upstream in the DPMT git repository) or make my own GitHub repository as an upstream source? Regards Gudjon
[toc] | [next] | [standalone]
| From | Dmitry Shachnev <mitya57@debian.org> |
|---|---|
| Date | 2018-01-13 09:10 +0100 |
| Message-ID | <v7p33-3dS-5@gated-at.bofh.it> |
| In reply to | #10032 |
[Multipart message — attachments visible in raw view] — view raw
Hi Guðjón, On Wed, Jan 10, 2018 at 09:21:47PM +0100, Guðjón Guðjónsson wrote: > Hi list > > I am updating my package pyqwt3d. It is tested for Qt5, python2 and python3. > The changes were so huge that I made GitHub fork of it: > https://github.com/GauiStori/PyQwt3D > > Now I have two questions: > > 1. Shall I skip the python2 version since it is already end of life? It looks like the current version of pyqwt3d has no reverse dependencies, and new applications will use Python 3, so yes, it makes sense to skip the Python 2 version. > 2. Shall I make my changes into a huge patch (changes from upstream > in the DPMT git repository) or make my own GitHub repository as an > upstream source? As the real upstream had no updates since 2009, and your changes are huge, I don’t see anything wrong in using your GitHub repository as upstream. -- Dmitry Shachnev
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web