Re: HELP: python-3to2 is marked for autoremoval from testing
Hi, >Not sure why is this on -mentors when -python exists, but oh well... it is also on -python, but with a bad subject that made it almost hide from the automatic messages :) >I'd put my bets on: >https://hg.python.org/cpython/rev/1206c64de875 thanks! >Have fun updating gen_printargs() or maybe map_printargs() in >lib3to2/fixes/fix_print.py. I tried, but it only made my head hurt. thanks for trying! I forwarded to lib3to2 developers the hint :) I hope somebody will come with some alternative solution then ;) Gianfranco
Re: HELP: python-3to2 is marked for autoremoval from testing
Not sure why is this on -mentors when -python exists, but oh well... * Gianfranco Costamagna, 2016-10-18, 21:14: 838974: python-3to2: FTBFS: AssertionError: 'print(*args)\n\n' != 'print *args\n\n' Does anybody have any clue why that test is now failing? I'd put my bets on: https://hg.python.org/cpython/rev/1206c64de875 I'm also considering a Python bug here, because it seems a regression to me Nope. Have fun updating gen_printargs() or maybe map_printargs() in lib3to2/fixes/fix_print.py. I tried, but it only made my head hurt. -- Jakub Wilk
HELP: python-3to2 is marked for autoremoval from testing
Hi Python Developers/mentors, (fixing the object of the email and forwarding to mentors) sometime ago, I packaged python-3to2, which is a dependency of python-guess-language (Python2 package). The guess-language is a Python3 package, and runs 3to2 to provide a Python2 compatible package (needed for w3af). Now, w3af needs that Python2 package, and I don't want to make guess-language both 3 and 2 compatible, because such change might be not trivial to do and I'm not a Python expert. So I would like to fix once more python-3to2, who started to FTBFS in testsuite with Python3.5 (I guess) https://bitbucket.org/amentajo/lib3to2/issues/50/testsuite-fails-with-new-python-35 >838974: python-3to2: FTBFS: AssertionError: 'print(*args)\n\n' != 'print >*args\n\n' Does anybody have any clue why that test is now failing? I'm also considering a Python bug here, because it seems a regression to me thanks for your help, Gianfranco