Re: CVS commit: pkgsrc/print/py-weasyprint

[Greg Troxel <gdt%lexort.com@localhost>]

Klaus Klein <kleink%kleink.org@localhost> writes:

> Am 15.11.2018 um 19:14 schrieb Joerg Sonnenberger <joerg%bec.de@localhost>:
>
>>> On Wed, Nov 14, 2018 at 06:17:26PM +0000, Klaus Klein wrote:
>>> Module Name:    pkgsrc
>>> Committed By:    kleink
>>> Date:        Wed Nov 14 18:17:26 UTC 2018
>>> 
>>> Modified Files:
>>>    pkgsrc/print/py-weasyprint: Makefile PLIST distinfo
>>> Added Files:
>>>    pkgsrc/print/py-weasyprint/patches: patch-setup.cfg
>>> Removed Files:
>>>    pkgsrc/print/py-weasyprint/patches: patch-setup.py
>>> 
>>> Log Message:
>>> py-weasyprint: Update to 43.
>> 
>> Thanks for updating to unusable versions...
>> 
>>> * Python 3.4+ is now needed, Python 2.x is not supported anymore
>
> I did actually ponder this, weighing against the feature set that came
> with 43... Anyway, I‘ll go ahead and just add py-weasyprint0 to cater
> to 27.

I am also tending  to want to stay on 27, but it seems the tide is
turning.

I wonder

  is there a real problem with python 34, like not building, or
  something truly troubling?

  is there a real issue for many of having 27 and 34 both (which happens
  to me a lot, at a cost of small bloat?

because it seems more and more things in the py world are deciding that
27 is ancient history.