Hi all, and thanks for putting this together, Zachary.
Just to chip in with my own context:
- I'd been pondering making this connection myself lately (due to the delays in getting Fabric 2 to parity and now Python 2's official EOL). Hi!
- Fabric 1.15 was IIRC a single small feature-add, so if there are no big changes on the fork besides just the Python 3 compatibility, unifying them should still be relatively easy, mechanically speaking.
- As stated earlier on the list, my main concern with the Py3 compat is that Fabric 1's test suite doesn't have as high a % coverage as I'd like (one of many impetuses for v2) but at this point I'm guessing fabric3's usage has been widespread enough, for long enough, that any serious bugs have already been found.
- Curious what, if any, you ran into though - Paramiko went through quite a lot of instability in its own Py3 journey...
- Re: the fabric3 name on pip - no rush on figuring that out, for multiple reasons.
- At the VERY least we would need to wait til stats show most users of fabric3 had migrated to either post-merge fabric1, or fabric2. Not in a rush to pull the rug out from under anyone.
- I'm hoping that Fabric 3.x, 4.x etc will be non full rewrites and thus there will be no need for in place side by side upgrades - which was the only real reason to even need a 'fabric2' on pypi (and, thus, ever a mainstream 'fabric3')
- By the time we get there I'd mostly be concerned about user confusion (intending to get 'fabric==3.x' but installing 'fabric3' instead) but that is likely a ways off!
Best,
Jeff