Honestly, that was my expectation as well, so I'll double check that today
- thanks a lot for the catch! Patchwork is currently the least-used of the
two contrib projects which is probably why this went unnoticed.
On Fri, May 4, 2018 at 5:20 AM, Max Arnold <lwa...@gmail.com> wrote:
> I was unable to install patchwork using Python 3.6 ("NameError: name
> 'execfile' is not defined"). I think it would be helpful to have py3
> compatibility matrix for the full set of
> utilities (fabric, patchwork, invoke, invocations). My initial
> expectations after reading the doc were that everything is Py3 ready
> *including* the contrib replacement.
>
> On Thu, Apr 26, 2018 at 04:18:51PM -0700, Jeff Forcier wrote:
> > I recently spent a bunch of time on a detailed upgrade doc, which can be
> > viewed here:
> >
> > http://docs.fabfile.org/en/v2/upgrading.html
> >
> > Feedback (other than "hey, why is my favorite feature not ported yet?")
> is
> > welcome - did I leave anything out, is anything too confusing, are there
> > typos, etc?
>
> _______________________________________________
> Fab-user mailing list
> Fab-user@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/fab-user
>
--
Jeff Forcier
Unix sysadmin; Python engineer
http://bitprophet.org
_______________________________________________
Fab-user mailing list
Fab-user@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fab-user
