Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #7207
| From | Barry Warsaw <barry@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Removing some python3-* packages |
| Date | 2015-08-24 23:30 +0200 |
| Message-ID | <q17tw-31O-11@gated-at.bofh.it> (permalink) |
| References | <pHSOm-6Yq-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Just a quick follow-up I've been meaning to send. On Jul 02, 2015, at 03:55 PM, Barry Warsaw wrote: >As part of the 3.5 test rebuild I noticed an incompatibility with >python3-enum, which I reported upstream. The response was: there's actually >no reason to have a Python 3 version of enum in any version >= Python 3.4. >Since that's all we have now, maybe it makes more sense to just remove the >python3-enum package from Debian. Which is what I'm going to do. I've interacted with upstream and there's just no reason for us to be shipping a Python 3 version of enum34, especially in Stretch given our current and future supported Python 3 versions. I'll be uploading a new version of enum34 that deletes python3-enum34 asap. py3porters, please keep this in mind and don't add it back. It'll ftbfs anyway and I'll close any related bug as won't fix. In general, I think we'll just have to take similar situations on a case-by-case basis. For packages which provide additional functionality not in stdlib Python 3, it may still make sense to provide a python3- version of the package. Cheers, -Barry
Back to linux.debian.maint.python | Previous | Next | Find similar
Re: Removing some python3-* packages Barry Warsaw <barry@debian.org> - 2015-08-24 23:30 +0200
csiph-web