I'd like to report that dev-python/pylint-0.9.0 works fine on amd64, ~amd64 can be added to KEYWORDS
* Byte compiling python modules for python-2.4 .. ... Compiling /usr/lib64/python2.4/site-packages/pylint/test/input/func_continue_not_in_loop.py ... File "/usr/lib64/python2.4/site-packages/pylint/test/input/func_continue_not_in_loop.py", line 8 continue SyntaxError: 'continue' not properly in loop Compiling /usr/lib64/python2.4/site-packages/pylint/test/input/func_syntax_error.py ... File "/usr/lib64/python2.4/site-packages/pylint/test/input/func_syntax_error.py", line 1 def toto ^ SyntaxError: invalid syntax Compiling /usr/lib64/python2.4/site-packages/pylint/test/input/func_unknown_encoding.py ... Sorry: MemoryError: () Compiling /usr/lib64/python2.4/site-packages/pylint/test/input/func_continue_not_in_loop.py ... File "/usr/lib64/python2.4/site-packages/pylint/test/input/func_continue_not_in_loop.py", line 8 continue SyntaxError: 'continue' not properly in loop Compiling /usr/lib64/python2.4/site-packages/pylint/test/input/func_syntax_error.py ... File "/usr/lib64/python2.4/site-packages/pylint/test/input/func_syntax_error.py", line 1 def toto ^ SyntaxError: invalid syntax Compiling /usr/lib64/python2.4/site-packages/pylint/test/input/func_unknown_encoding.py ... Sorry: MemoryError: () [ !! ] don't work fine here.
This bug is not linked to amd64 see http://bugs.gentoo.org/show_bug.cgi?id=97506 I think it's just a problem in the ebuild You also miss some important output in you message emerge =pylint-0.9.0 .... SyntaxError: invalid syntax Compiling /usr/lib64/python2.4/site-packages/pylint/test/input/func_unknown_encoding.py ... Sorry: MemoryError: () [ !! ] >>> Regenerating /etc/ld.so.cache... >>> dev-python/pylint-0.9.0 merged. >>> clean: No packages selected for removal. >>> Auto-cleaning packages ... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. bou ~ # pylint --version No config file found, using default configuration pylint 0.9.0, astng 0.14.0, common 0.13.0 Python 2.4.2 (#1, Jan 14 2006, 13:15:06) [GCC 3.4.5 (Gentoo 3.4.5, ssp-3.4.5-1.0, pie-8.7.9)]
This noisy output is harmless but should no longer be occuring in pylint 0.9.0. What version of pylint are you hitting this with?
Okay, I'd love to keyword 0.10.0 as ~amd64, but I have some thoughts first. I get that the tests are supposed to fail, but presently it could be disturbing to the user to see them fail and not know that they're supposed to. (The errors that Metalgod pointed to in comment #2). We should have some sort of clear message to the user indicating that. Also, the ebuild should run python_tkinter_exists because right now attempting to run pylint-gui just dies unless you compiled python with USE="tcltk"
The tests are not supposed to fail. The ones I know are failing are not run by src_test, and none of the files causing messy output in the .pyc/.pyo compilation phase are installed. Can you tell me what tests are failing for you? I prefer not to check for tkinter in the ebuild because pylint (not pylint-gui) is quite useful without tkinter (don't want to force a python-with-tcltk dep on everyone). Would it work for you if I apply a gentoo-specific patch to pylint-gui to fail with a sensible error message if tkinter is not available?
I'm seeing these: https://bugs.gentoo.org/show_bug.cgi?id=120771#c1 and because of the function names I had assumed they are supposed to be there as a confirmation. As for the tkinter, I agree, it would be much more useful to me to never use the gui I just don't like the idea of putting a binary on a system that we know is likely broken. Your suggestion would be fine by me.
Sorry for the delay. This should be fixed in pylint-0.11.0, please test.
I can confirm that pylint-0.11.0 builds and seems to be working fine on ~amd64
looks like ~amd64 was added 11 Jun 2006 by genone.
