Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11764
| From | Diane Trout <diane@ghic.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Should python-cloudpickle get a py2keep tag? |
| Date | 2019-09-05 20:50 +0200 |
| Message-ID | <yD4Zr-5bj-11@gated-at.bofh.it> (permalink) |
| References | <yD4wp-4Wm-5@gated-at.bofh.it> <yD4wp-4Wm-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, 2019-09-05 at 20:14 +0200, Matthias Klose wrote: > > you are asking about the least preferred option, without telling why > you can't > convert to python3, or why you can't remove the affected > packages. If you have > both spyder and spyder3 (Python3?), then why not drop spyder? I > didn't look at > skimage, but maybe look there first if it needs to be Python2. > I was assuming that py2keep was a temporary flag that would be removed after the leaf packages get fixed. Since spyder and skimage are under the science team I wasn't sure how long it would take for them to get around to removing the python2 packages. Both spyder and skimage packages have python3 versions. spyder does install into /usr/bin/spider so it's removal will have a bigger impact on end users than something that's just a python package. I did upload a new version of cloudpickle last night 1.2.1-1 with Python2 removed, I'm trying to figure out if I should let the dependencies just live with the previous python-cloudpickle 0.8.0 package or if I should upload a new version of 1.2.1 with the python2 packaging built. Diane
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Should python-cloudpickle get a py2keep tag? Diane Trout <diane@ghic.org> - 2019-09-05 20:20 +0200
Re: Should python-cloudpickle get a py2keep tag? Matthias Klose <doko@debian.org> - 2019-09-05 20:20 +0200
Re: Should python-cloudpickle get a py2keep tag? Diane Trout <diane@ghic.org> - 2019-09-05 20:50 +0200
csiph-web