from
Andreas Amoroso <a.amoroso at web dot de>
to
Sylvain Thenault <syt at logilab dot fr>
subject
New PyLint release
date
Hello again,2004/05/13 21:24
nice to see that the new release is out already. I took the opportunity
to find out what the problem was that I had the last time installing
PyLint. I build a binary installer using setup.py bdist_wininst and got:
C:\>setup.py bdist_wininst
running bdist_wininst
running build
...
adding 'PURELIB\logilab\common\ureports\text_writer.py'
adding 'PURELIB\logilab\common\ureports\__init__.py'
creating dist
removing 'build\bdist.win32\wininst' (and everything under it)
Traceback (most recent call last):
File "C:\setup.py", line 179, in ?
install()
File "C:\setup.py", line 163, in install
stream = open(product_init, 'w')
IOError: [Errno 2] No such file or directory:
'build\\bdist.win32\\wininst\\PURELIB\\logilab\\__init__.py'
Using setup.py install creates the __init__.py as expected, using the
binary installer does not. Obviously, creating the binary installer on
Win is/shows the problem. This is not at all important, but using Win
its still nice to install Python modules this way. Maybe it would be
worth fixing it in a future release. (You are on *nix, right?)
BTW, IMHO the naming convention for the module-specific PyLint output
file is - well - not what I would have chosen. Don't you think something
like PyPosta.pylint.txt or even (consistent to global file name)
pylint_PyPosta.txt would be nicer than PyPosta,pylint.txt?
Best regards,
Andreas

