[python3-pysam + iva] - Pysam depends on pyrex
Good morning, This is just like a Matryoshka doll... So I tentatively started packaging python3-pysam. Still haven't created a git alioth project for it. I did clone the python-pysam project [1], in hopes that it would be just a couple of minor changes. Only to find that pysam depends on python-pyrex. So to package python3-pysam, I have also to packge python3-pyrex. It seems that python-pyrex has not seen much development [2]. Is anyone working on this package? Sorry to be a pain, but it really starts to feel like a pontless task to be packaging iva... I don't know what to expect from this email. I suppose it's more of a rant. Best, Jorge [1] - http://anonscm.debian.org/cgit/debian-med/python-pysam.git/ [2] - https://tracker.debian.org/pkg/pyrex
Re: Dependency on ‘python-lockfile’: API breakage in version 0.9
On 26-Nov-2014, Thomas Goirand wrote: > On 11/26/2014 09:29 AM, Ben Finney wrote: > > The ‘lockfile’ upstream changed the API as of version 0.9 > > https://code.google.com/p/pylockfile/source/browse/trunk/RELEASE-NOTES>, > > and dependent Python code will not work until it uses the current API. > > Would it be possible to work with upstream to avoid such breakage? > It doesn't seem reasonable at all to me to have API breakage It isn't good, I agree. I did work with the upstream at that time, and they did attempt to address this (incrementing the minor version, providing factory functions), but I was unaware the API breakage was planned until a new version was already released. > I believe it's our role as a distribution to work with upstream to > avoid such craziness. Maybe upstream doesn't understand the > importance of a stable API, and it would be worth explaining how bad > such breakage is. What is your view here? I agree with all that. I did attempt to educate upstream about the importance of providing an upgrade path, but it wasn't enough in this case. It's very difficult to get most upstream Python developers to care much about API stability, especially in a culture where “install everything into a virtualenv and ignore the OS package manager” is the normal mode of thinking. I'd love all Python library upstreams to take https://wiki.debian.org/UpstreamGuide> to heart, but the current reality is that most do not at this time. May the education campaign continue; in the meantime, I need package maintainers to help clean up that mess. -- \ “Technology is anything that wasn't around when you were born.” | `\ —Alan Kay | _o__) | Ben Finney signature.asc Description: Digital signature
Re: [python3-pysam + iva] - Pysam depends on pyrex
Ok, Rant is over. I have just been in touch with the pysam developers and they assured me that pysam only depends on Cython and not on pyrex. Pyrex is still stated as a dependency of python-pysam. I am thinking of making changes to the python-pysam package for it to create a new binary python3-pysam. I will test if removing the python-pyrex dependency breaks the package. Regards, Jorge On Wed, Nov 26, 2014 at 9:08 AM, Jorge Sebastião Soares < j.s.soa...@gmail.com> wrote: > Good morning, > > This is just like a Matryoshka doll... > So I tentatively started packaging python3-pysam. > > Still haven't created a git alioth project for it. > > I did clone the python-pysam project [1], in hopes that it would be just a > couple of minor changes. > > Only to find that pysam depends on python-pyrex. > > So to package python3-pysam, I have also to packge python3-pyrex. > > It seems that python-pyrex has not seen much development [2]. > > Is anyone working on this package? Sorry to be a pain, but it really > starts to feel like a pontless task to be packaging iva... > > I don't know what to expect from this email. > > I suppose it's more of a rant. > > > Best, > > Jorge > > > > [1] - http://anonscm.debian.org/cgit/debian-med/python-pysam.git/ > [2] - https://tracker.debian.org/pkg/pyrex >
