Source: libpeas Severity: wishlist -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Dear Maintainer, As we move to a world dominated by Python 3, we are trying to reduce the dependencies on Python 2 in Debian and derivatives. libpeas is a problem because the package links against both Python 2 and Python 3. I don't know whether it makes sense to support both at the same time, but it definitely makes sense to have a version that only supports Python 3. For example, in Ubuntu we want to remove Python 2 from the default images, but we can't do that with a libpeas that links against both Python 2 and 3. At the least, we need a libpeas built without --enable-python2. Questions: * Does it also make sense to have a libpeas built without --enable-python3? * Does it still make sense to have a libpeas built with both --enable-python2 and --enable-python3 as is currently the case? - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJWXhVBAAoJEBJutWOnSwa/UG0P/3kPG+wfjtxlM2Ht0zkCJQKa lB6jiBNOHjm+AJbhYaQMdfvuCLy8z7fXn8NVgyJtlEEBlD8mwjl7e5LrYSgXFmoN wdYAbJohckVVjhOEek6vsvX5YU9JGSR/np0aA1B1gkxKZBIUfIzdPiTX446kTOyg X/EdXLpz5EwWPJLZavxSBe4BC09VNmCB+zUXllIjgIBb/xqSsstkVODAjjO3hAcc JQF0lfUqRAYwCFhvb99qiSvx/NDluzAHOt2NVaYOCMVEealpIKFAK8sncltXrRX2 ocHlqhooCKIbv0+p75LVdN1MrCJcXPp/umriL88jxYsnC3Wb8Opw873FdglaeapV bkhBfODmx0rQTBwmGJSR2u05/506sLTmGfLg5xyBF81nE7WzBmeXnOkDrn+NIihl 0mrvChgYUfpMzQiWOBN2qnZ1KtsrekPYeQyLi6znKjhUQXDqmghQM5uSpn4o0Aqw YCLN5Z5slsOZIJ1wFg2x8jWS5/lSG4duuXhVN8TdWb8Kp3FAKVxO30fEREKSxC7c Bpk0PJWpgwCW+lLPL2ggHUymGWlS5kX/NUkR+vQ5JZ4RyVGeyvBY+X9/iL+yxEfU EdCAQOTM/0sSJFSIwC0m8LFTSrmPJ4fWjk4fM+yEWkJezwLpSHaDlsUPIMWSvpMM FmRIQriklAzmUc5sprdY =Sa0W -----END PGP SIGNATURE-----