Bug#1068488: RFP: iterable-io -- Adapt generators and other iterables to a file-like interface

[Antoine Beaupre]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org

* Package name: iterable-io
  Version : 1.0.0
  Upstream Contact: Carey Metcalfe 
* URL : https://pypi.org/project/iterable-io/
* License : LGPLv3
  Programming Lang: Python
  Description : Adapt generators and other iterables to a file-like 
interface

iterable-io is a small Python library that provides an adapter so that
it's possible to read from iterable objects in the same way as
file-like objects.

It is primarily useful as "glue" between two incompatible
interfaces. As an example, in the case where one interface expects a
file-like object to call .read() on, and the other only provides a
generator of bytes.

One way to solve this issue would be to write all the bytes in the
generator to a temporary file, then provide that file instead, but if
the generator produces a large amount of data then this is both slow
to start, and resource-intensive.

This library allows streaming data between these two incompatible
interfaces so as data is requested by .read(), it's pulled from the
iterable. This keeps resource usage low and removes the startup delay.



this is a new dependency introduced by magic-wormhole 0.14

Adopting pychm (Was: Packaging multivolumefile?)

[Andreas Tille]

Hi Hiroshi,

Am Sat, Apr 06, 2024 at 02:51:51AM +0900 schrieb yokota:
> Thanks a lot for your detailed document.

You are welcome.

> I will try to fixup other packages.

Just ping me once done.

> PS:
> If py7zr is done, I will also try package pychm to use for Debian
> Calibre package.
> Please sponsor me for pychm package if you have time.

I'll try in any case.  It should be some change of maintainer
+ close bug and - as I'd recommend - some

routine-update -f

away.

Just let me know once you are ready

  Andreas.

> > O: pychm -- Python binding for CHMLIB - Python 3
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065222
> 
> --
> YOKOTA Hiroshi
> 

-- 
https://fam-tille.de

Re: Packaging multivolumefile?

[yokota]

Hi Andreas,

Thanks a lot for your detailed document.
I will try to fixup other packages.

PS:
If py7zr is done, I will also try package pychm to use for Debian
Calibre package.
Please sponsor me for pychm package if you have time.
> O: pychm -- Python binding for CHMLIB - Python 3
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065222

--
YOKOTA Hiroshi

Fwd: [cdent/paste] Potentially ceasing development of Paste (Discussion #91)

[Alexandre Detiste]

Might interrest more here.

-- Forwarded message -
De : Chris Dent 
Date: ven. 5 avr. 2024, 19:18
Subject: [cdent/paste] Potentially ceasing development of Paste (Discussion
#91)
To: cdent/paste 
Cc: Alexandre Detiste , Mention <
ment...@noreply.github.com>


paste uses a lot of deprecated functionality, much of it related to old
libraries like cgi and cgitb.

When Python 3.13 becomes the main Python release this deprecated
functionality will be removed and without a fair bit of work paste will
stop working.

I personally do not think we should continue to maintain paste. It is an
old tool using old technology that is no longer aligned with modern
techniques or tools.

I would like us to consider winding it down but I'm not certain who should
be involved in the discussion so pinging some of the people who have made
contributions to the project over the last while: @a-detiste
 , @amitmarkel 
, @benjaminp  , @Cito
 , @cjwatson  ,
@CyrilRoelandteNovance  , @blueyed
 , @brondsem  ,
@hugovk  , and of course @ianb
 .

Please register your opinion.

If you feel like paste should carry on living, and want to volunteer to
take over maintenance I'm very willing to transfer ownership.

I also maintain pastescript and feel it should end too, so if someone wants
to take them as a package deal that would be great.

—
Reply to this email directly, view it on GitHub
, or unsubscribe

.
You are receiving this because you were mentioned.Message ID:

Re: Packaging multivolumefile?

[Andreas Tille]

Hi Yokota,

Am Tue, Apr 02, 2024 at 08:39:36PM +0200 schrieb Andreas Tille:
> > Nevermind, YOKOTA Hiroshi already has done this and more and is looking
> > for sponsors.
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065221#17
> 
> Thanks a lot for your packaging work.  My very personal sponsoring
> policy is that I sponsor only team maintained packages.  If you move
> your packages to DPT I'll happily sponsor your work. 

Thanks a lot for all your work on the said pre-requisites and moving
them to DPT.  For the moment I've picked python-multivolumefile and
python-bcj and uploaded them to New queue.  My sponsoring style is to do
additional commits trying to be as verbose as possible to tell the
sponsee what to change and why.  I hope you like this.  When looking
at these two packages I've noticed a pattern of changes that were needed
to fix lintian info messages.  Please make sure to run

   lintian -I PACKAGE_VERSION_amd64.changes

to learn about what changes might be sensible to silence lintian.
Some of them where cosmetic but I try to fix these to make sure the
lintian output is not too noisy and I might miss something that
might really need fixing.  I'd also recommend:

$ grep -v ^# ~/.lintianrc 
color=always
display-info=yes

I hope my commits are sensible to you - if not please ask back.

As a general remark:  In those teams I'm more involved we have the
tradition that sponsees leave the distribution in d/changelog to
UNRELEASED while the sponsor changes this to unstable before the final
upload.  This helps team members to immediately know about the status.
I'd be happy if you would follow this as well.

Please verify that your other packages are fixing the things I
commited to the two example packages.  If time permits I'd happily
sponsor you other packages (if nobody else in the team will beat
me in doing so).

Thanks again for all your work
   Andreas.

-- 
https://fam-tille.de

[RFS] -- pmbootstrap 2.2.1

[Vivek K J]

Hey team,

 I've updated pmbootstrap package from 2.1.0 to 2.2.1. Current version
of the package is unusable because of #1065637 [1]. The updated package
is available at
https://salsa.debian.org/python-team/packages/pmbootstrap. Requesting
for sponsorship.


[1] - https://bugs.debian.org/1065637
-- 
Regards,

Vivek K J
Debian Maintainer
---
 .''`.
Personal Website:  https://vivekkj.in   : :'  :
GPG Key: D017 9263 E202 0E40 7157  4073 A5FF 4BB3 EA53 C5DF `. `'`
  `-

OpenPGP_0xA5FF4BB3EA53C5DF.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Request to join the team

[Ricardo B. Marliere]

On  3 Apr 15:48, Pierre-Elliott Bécue wrote:
> Hi Ricardo,
> 
> "Ricardo B. Marliere"  wrote on 29/01/2024 at 
> 23:07:59+0200:
> 
> > Hi,
> >
> > My name is Ricardo and I've been trying to get involved with Debian to
> > give back to the community. I'm "rbmarliere" in Salsa [1] and I have
> > made a few contributions to the Go team. However, I have more experience
> > with Python and would like to help in fixing bugs for the team and
> > other general QA work. I have read and accept the Debian Python Team
> > Policy [2].
> 
> Considering your past contributions, I've granted you a Developer access.

Thank you Pierre! I'll go look for things to help with :)

> 
> Feel free to reach out when you need new repos created.
> 
> On the long-term if you contribute, I'll be happy to extend your ACLs.
> 
> Thanks, and sorry for the delay.
> -- 
> PEB

Re: New upstream version for python-pint

[Antonio Valentino]

Dear Alexandre, dear Thomas,

Il 01/04/24 21:32, Alexandre Detiste ha scritto:

I've packaged font-awesome5 at work, for sure it's not in Debian.

The upgrade to v5 was rightfully reverted but it's in limbo since.

https://packages.debian.org/sid/fonts-font-awesome

fonts-font-awesome (5.0.10+really4.7.0~dfsg-4.1)  <--
Please note that this package provides Font Awesome 4
(not Font Awesome 5 or Font Awesome 6 which are different fonts with
different licensing).


Thanks for the info.


Le lun. 1 avr. 2024 à 21:26, Antonio Valentino
 a écrit :


Dear Thomas,

Il 01/04/24 17:52, Thomas Goirand ha scritto:

On 3/31/24 21:05, Antonio Valentino wrote:

Dear Thomas,

Il 30/03/24 22:25, Thomas Goirand ha scritto:

On 3/29/24 15:13, Antonio Valentino wrote:

Dear Thomas and Ondřej,
a couple of packages that I maintain are impacted by an RC bug in
python-pint (#1067318).
I think that an update to the to the latest pint version 0.23 should
be sufficient to fix the issue.

If you agree, I would like prepare the package for the new upstream
version in the salsa.
Of course I will let to you the review and upload.

Please let me know,


kind regards


Please go ahead and feel free to add yourself as uploader.

Thomas


Thanks Thomas
The packages is now updated in salsa.
Unfortunately the reprotest job fails in CI, but I'm not able to
reproduce on my laptop and it seems not to be a regression.
I will try to fix it in future uploads but for the moment I would
prefer to have an upload to fix a couple of RC bugs.

Could you please review and upload?

I have also put myself as uploader.
I'm a DM so I kindly ask you to grant me upload permissions as
described in [3].


kind regards


Hi!

Thanks for the work Antonio.

1/ In the clean target, please also clean:
- Pint.egg-info
- docs/savefig

2/ There's a typo in d/changelog, you wrote: "d/copuright".

3/ I'm really not sure about the python-pint-doc.lintian-overrides
overriding "font-in-non-font-package". Can't you use the fonts from
system instead?

Cheers,

Thomas Goirand (zigo)


1/ and 2/ are now fixed

For 3/ I indeed did a quick search but I was not able to find a font
package providing the needed fonts

$ apt-file search fa-brands-400.ttf
gnunet:
/usr/share/doc/gnunet/html/_static/vendor/fontawesome/6.1.2/webfonts/fa-brands-400.ttf.gz
icinga-php-library:


[CUT]



Maybe node-fortawesome-fontawesome-free, but the version seems not to be
the same.
Actually I'm not really sure where these fonts are collected during the
build process.

Do you have any hint?


Ok, I think that the most convenient solution at the moment is to 
replace the vendored fonts with the ones provided by the 
python3-pydata-sphinx-theme package. This is not ideal because 
python3-pydata-sphinx-theme vendors the fonts itself but at least we 
avoid duplications.


The change is already in salsa.
Please Thomas, let me know if this is acceptable for you.

Unfortunately the package is not currently buildable because of an 
update in python3-lxml that determined #1068349 [1]



[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068349


kind regards
--
Antonio Valentino