Unable to run after clean install about tidypy HOT 4 CLOSED

Yea, flake8 just made a release that tossed a wrench in our works. I'll try to have a fix out tonight.

Dependency hell strikes again. :(

from tidypy.

New version published that should solve this. Let me know if problems persist.

from tidypy.

Awesome. Thanks! 👍

Was this caused by flake8 publishing a backwards-incompatible change without bumping versions correctly, or could this be solved by stricter dependency management on tidypy? Happy to brainstorm ideas if the latter - unless you already have a plan in place.

from tidypy.

flake8 didn't really do anything wrong, tidypy was just a victim of pip's limited ability to solve non-trivial dependency graphs.

Below are snippets from the output of pipenv graph for versions 0.6 and 0.7 of tidypy. tidypy depends on pycodestyle and pep8-naming. pep8-naming dependency chain includes a very loose dependency on flake8. When pip went to install flake8, it grabbed the newest, which requires a version of pycodestyle that was outside the bounds that tidypy wanted -- thus the error.

v0.6.0:

  - pep8-naming [required: >=0.4,<0.8, installed: 0.7.0]
    - flake8-polyfill [required: >=1.0.2,<2, installed: 1.0.2]
      - flake8 [required: Any, installed: 3.5.0]
        - configparser [required: Any, installed: 3.5.0]
        - enum34 [required: Any, installed: 1.1.6]
        - mccabe [required: >=0.6.0,<0.7.0, installed: 0.6.1]
        - pycodestyle [required: >=2.0.0,<2.4.0, installed: 2.3.1]
        - pyflakes [required: >=1.5.0,<1.7.0, installed: 1.6.0]
  - pycodestyle [required: >=2.3,<2.4, installed: 2.3.1]

v0.7.0:

  - pep8-naming [required: >=0.4,<0.8, installed: 0.7.0]
    - flake8-polyfill [required: >=1.0.2,<2, installed: 1.0.2]
      - flake8 [required: Any, installed: 3.6.0]
        - configparser [required: Any, installed: 3.5.0]
        - enum34 [required: Any, installed: 1.1.6]
        - mccabe [required: >=0.6.0,<0.7.0, installed: 0.6.1]
        - pycodestyle [required: >=2.4.0,<2.5.0, installed: 2.4.0]
        - pyflakes [required: >=2.0.0,<2.1.0, installed: 2.0.0]
        - setuptools [required: >=30, installed: 40.4.3]
  - pycodestyle [required: >=2.4,<2.5, installed: 2.4.0]

I thought about explicitly pinning flake8 in tidypy's dependencies to something known to be safe, but something feels dirty about forcing a dependency on something tidypy doesn't actually depend on. Also, it feels like a slippery slope, as there are other packages that could potentially cause the same sorts of issues (enum34, configparser, mccabe, etc), and pinning the entire tree feels bad, too.

I'm definitely open to suggestions, but I'd like to avoid things like vendoring everything or pinning the full dependency tree. For the time being, I've updated the cron on Travis to do a build every day, so if a release does sneak by that breaks tidypy, I'll at least get a notification.

from tidypy.