Update for fabric3.0

[LecrisUT]

• Resolve issues for fabric 3.0
• Pep621 modernization
• Changed .format to fstrings for more readability

Fixes: #41
Depends-on: #47

[bpluly]

Just as commentary, patching with this I was able to install the library and everything seems fine, I don't have all the test tools and haven't addressed that. I did wonder why setup.py was removed as it should still install with a toml file. Unless this is part of the work in progress it's worth calling it out in the PR.

[LecrisUT]

The change from setup.py to pyproject.toml is just implementing PEP621 since most projects are/should be migrating to it. That part is finished. For this PR, the only reason it is in draft is because I don't feel confident without getting the pytest running. The test method implemented also seems to contradict the recommended approach using MockContext. If you have any hints on how to get the tests I can translate them over.

[LecrisUT]

Ok, the tests are running again. I was missing a dependency. I'll try to see if I can fix the test failures. Failed docs are related to docstring, got no idea how to fix those.

[bitprophet]

Thanks for poking at this. I don't have a lot of time to dig right now but hopefully sometime soon-ish.

I did notice you set the dep to fabric>=3 - the backwards incompat changes in 3.x were quite minor (the big one was just dropping Py<3.6 support, which is handle-able by users' pips) so it's not clear to me what exactly broke here under 3.x. I think it's more likely the breakage was on 2.x (which was a total rewrite) and you should be able to set the pyproject field to >=2 instead?

[LecrisUT]

@bitprophet I've highlighted the main changes. Others were stylistic changes. And indeed, at least from the pytest, there didn't seem to be anything drastically changed, the only one seems to be with parsing the docstring, if you can assign someone to take a look at that, that would be wonderful

[LecrisUT]

invocations.travis was dropped.

[LecrisUT]

invoke does not bundle six, moved to str

[LecrisUT]

@bitprophet I hope the CIs here help. Please check the runs on my fork until the github action is enabled.

Are you ok with updating the minimum python requirement to 3.7? 3.6 does not support PEP621

[JoshYuJump]

@bitprophet I hope the CIs here help. Please check the runs on my fork until the github action is enabled.

Are you ok with updating the minimum python requirement to 3.7? 3.6 does not support PEP621

Python 3.7 has reached EOF, may by minimum python requirement should be 3.8

[SamuelMarks]

I'm supporting 2.7, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10, 3.11, 3.12 with Fabric and Patchwork. Would be great if this could be merged without breaking support for 3.5+ (so I can easily remain on Fabric 2.7.1 on python_version<'3.5' and newer versions later)

[LecrisUT]

@SamuelMarks If you want, you can run these tests on your fork with the minimum Python version you wish, and report back the patches needed to make it compatible. I don't remember if I checked the minimum requirements below those versions

[SamuelMarks]

@LecrisUT Only just got the chance. It should now support Python 2.7 (added the older setup.py which is compatible with older versions)

[geoffrey-eisenbarth]

@bitprophet Any movement on this? Thanks :)