Bug#807432: RFS: python-jellyfish/0.5.1-1 [ITP]

[Gianfranco Costamagna <costamagnagianfranco@yahoo.it>]

control: tags -1 moreinfo

Hi

>I'm quite certain that it is indeed a problem with the README (the

>library was initially only available on Python 2, and the README.rst has
>not gone through significant changes since then, even if Python 3
>support was introduced around 0.3.2). I'll follow up on upstream,
>hopefully resulting in a quick fix indeed.


FWIW adding "u" to the strings indeed fixed the issue
e.g. 'string' becomes u'string' (IIRC forcing unicode)
>My apologies if I should have explicitely mentioned it earlier: the
>conflicts with the existing "jellyfish" Debian package were noticed
>earlier on [1], and a recent discussion on the ITP bug [2] resulted on
>an agreement with the jellyfish maintainer that basically should result
>in:
>- the *existing* python-jellyfish should have its python module name
>renamed (work in progress at [3]).
>- this package should indeed be renamed to something else (
>"python-jellyfishstr" being the most likely candidate), and keep the
>python "jellyfish" module name.>
>
>I was waiting on #819016 being closed before making the changes to this
>package (renaming + uploading to the debian-python git + adding the VCS
>control fields) - again, sorry if it should have been stated more
>clearly that the package was not ready for uploading yet due to the
>naming/module conflicts.
>
>I'd be happy to proceed with the renaming right away, if that's ok - in
>regards to the BTS, would it be preferable to use the control tags
>(reopen, retitle, block on #819016?) or just submit a new ITP+RFS

>entirely?

block -1 by nnn is fine.



a ping when the other package is renamed and in testing even better.

BTW, the Python policy is something like
"python-foo" means "import foo" works.
Adding str migth deviate from the policy, you might want to ask #-python
about this specific issue (and quote the conversation here)

thanks, I'll wait for your action,

Gianfranco