Try to fix an AttributeError related to pycodestyle 2.11.0

[paugier]

This could fix #689 (see also #1191).

Note that I have no idea of the consequence of this simple change... However, it would be interesting to check if the tests could succeed with pycodestyle 2.11.0.

[codecov-commenter]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (5b9110b) 97.83% compared to head (f961833) 97.83%.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #699   +/-   ##
=======================================
  Coverage   97.83%   97.83%           
=======================================
  Files           1        1           
  Lines        2398     2402    +4     
=======================================
+ Hits         2346     2350    +4     
  Misses         52       52           

Files Changed	Coverage Δ
autopep8.py	97.83% <100.00%> (+<0.01%)	⬆️

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[shaperilio]

@paugier thanks for this; currently flake8 6.1.0 claims it needs pycodestyle 2.11 so we're in a bind here. They combined white space checks into one and autopep8 has them separated.

A potential issue I see here is that you made a change in fix_e225 and fix_e231 is just below it. These are the two things that got merged on the pycodestyle side. So I would:

1. Put a comment somewhere in there explaining why you had to make this change, and that these two checks got merged, and
2. Check if fix_e225 also fixes E231, in which case we should probably clean this up a bit more.

(Trying to avoid a situation down the road where someone wonders e.g. why fix_e231 never gets called, etc.)

[shaperilio]

#699, #696, #691, #690 are all the same. I suggest someone look into this comment and push their PR forward with a solution.

[hhatto]

thanks for contribution.
This has been fixed in pull-request #696, so we will close this one 🙏
We will release a new version within a few days.