(flake8py33) C:\Windows\System32>easy_install flake8
Searching for flake8
Best match: flake8 1.7.0
Running flake8-1.7.0\setup.py -q bdist_egg --dist-dir c:\users\lambacck\appdata\local\temp\easy_install-cjnnp3\flake8-1.7.0\egg-dist-tmp-vku6sa
zip_safe flag not set; analyzing archive contents...
error: c:\users\lambacck\appdata\local\temp\easy_install-cjnnp3\flake8-1.7.0\build\bdist.win32\egg\flake8\tests\__pycache__\test_flakes.cpython-33.pyc: The process cannot access the file because it is being used by another process
pip install flake8 goes much better, an install works and a flake8.cmd is installed and running flake8 results in a help prompt.
There is no exe created because on Python 3 no attempt is made to import setuptools and add the console_scripts entrypoint.
I can't say why it doesn't work with easy_install but Christopher Lambacher has the right explanation for the absence of the exe on py3.
I had a few discussions with Tarek Ziadé when I did the change to add the cmd (w/o setuptools) and exe (with setuptools) to the install. I believe he was considering important not to force the package to depend on setuptools. It seems flake8 now has a dependency on pep8 instead of being embedded, we might reconsider that since pep8 has a dependency on setuptools.
I haven't played a lot with py3 so far but I'll give it a try as well and see what I can do.
Thx Ian Cordasco, it seems the push you did resolved the problems I had with flakey previously. I updated my fork by adding the missing entry points for the exec creation. There are a few things worth noting though, I am not sure if these are known issues or not.
flakey is not in the install_requires
distutils test command fails on 2.7 with an import error on from flakey import check (should be checker I guess?)
I get the same errors with nosetests
distutils test command on 3.3 doesn't seem to run anything.
flake8 distutils command fails as well
Because of that, I haven't enabled the flake8 entry point and test dependency on nose.
Marc Labbe We're moving back off of flakey onto pyflakes. Pyflakes 0.6.1 is far better than flakey will every be. I'm not sure about your second point, but I'll check into it in the morning. And they weren't known to me (at least), thanks for reporting them.
Marc Labbe I tried reproducing the things you mentioned. With python 2.6 the distutils test command passes for me (except after the tests are run, there's an exception in with atexit which is not our fault). On python 3.2+, distutils tells me that install_requires is an unknown distribution option and then tells me that test is an invalid command. This is extraordinarily bizarre.
I fixed the tests though. My old virtualenv was polluted with an installation of flakey which is why I didn't see any of the problems. Thanks for pointing that out.
Ugh, I replied to this via email but it didn't go through... Here's what I had said:
Hi Ian Cordasco, I didn't know flakey before seeing it in this project, w/o 0 (#56)
context I thought it was going to be a replacement for pyflakes :)
Yep. Pyflakes development was just about dead and we needed things fixed in a
manner that worked on both python 2 and 3. So... I forked pyflakes3k and made
it work under python 2 and got a few other things fixed up for it. But thens
Florent Xicluna got himself the responsibility of being a/the maintainer for Pyflakes
and released 0.6.1.
instal_requires is a setuptools command only, check if you have it
installed when generating the package, especially given the message you get already set, don't override (#1161)
on 3.2. You probably have it in your 2.6 installation.
Ah so we/I have to fix this as an extra option. Should we then print a message
for the user (if they're not using distribute/setuptools) to install pep8 and
The same goes for python setup.py test which I mistakenly said was a distutils command while it is available only from setuptools/distribute.
Ah good. At least I'm not crazy. :-)
Overall, I think all the test issues were all related to the bad import I mentioned.: 422 Validation Failed" will occured if miles
I'll try to get you more detailed info tomorrow about everything. I admit I wrote that pretty quickly. I should be able to fix those issues myself given a free hour to spare.
No worries. If you don't have the time, let me know.
I'll spend some time to enable the distutils flake8 command I didn't enable for py3 as well. It should be trivial. Should I open an issue?
It's up to you. We can probably continue using this and you can just open a
pull request and we should be fine.