Summary: | dev-python/singledispatch and virtual/python-singledispatch new ebuilds | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Timo Rothenpieler <timo> |
Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | proxy-maint, realnc |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 518744 | ||
Attachments: |
dev-python/singledispatch-3.4.0.3.ebuild
virtual/python-singledispatch-0.ebuild |
Created attachment 384086 [details]
virtual/python-singledispatch-0.ebuild
Nikos, would you like to maintain this packages too? Or maybe somebody from Python herd maintainers want? (In reply to Sergey Popov from comment #2) > Nikos, would you like to maintain this packages too? > eeer who is Nikos? > Or maybe somebody from Python herd maintainers want? ........! Whoever Nikos is see me about proxy maintaining it under my support, however the same equally applies to timo@rothenpieler.org Nikos, tell us (here or proxy-maint@) if you want to maintain these and I will push them to the tree for you When you commit it, please also update the wiki [1]. [1]:https://wiki.gentoo.org/wiki/Project:Python/Virtuals (Sorry for the delay.)
> Nikos, tell us (here or proxy-maint@) if you want to maintain these and I
> will push them to the tree for you
Yes, since singledispatch is needed by livestreamer for Python <3.4, I can maintain them together.
(In reply to Markos Chandras from comment #4) > Nikos, tell us (here or proxy-maint@) if you want to maintain these and I > will push them to the tree for you ok you do it then I am a bit confused about the virtual and bare in mind I don't understand python very well. Does the virtual satisfy the "either python3.4 or the singledispatch package" requirement? Anyone to address my comments? ping again singledispatch is a feature that is part of python3.4. Prior versions need the external library. So packages which needs singledispatch just depend on the virtual and get either a recent enough python or the library. Thanks. Since you have done all the work here, would you like to maintain it as well? Ian Delaney has committed it before I did myself so closing this bug. |
Created attachment 384084 [details] dev-python/singledispatch-3.4.0.3.ebuild This backports the functools.singledispatch library from python 3.4 to python 2.6-3.3.