>
> Once a package is popular
> enough, it will get "promoted" to the main community repo. That should
> either never happen since there's not many fabric1 users, or happen
> after python3 migration.
>
> To avoid also making python2-pytest-relaxed and python2-invoke,
> python2-paramiko doesn't run
Hi Mathias et al,
Apologies, thought I had followed up last month, but not seeing anything in
my outbox...
I am definitely willing to merge PRs that add Python 3 compatibility,
though my assumption was that we'd do it as a single PR that approximates
the diff between the official repo's v1
