Hi, I do make use of a (modified version) of the included fabfile. However, I'm using Python 3.6 on my dev and server machines, and use Fabric3 to do the deployment. It works pretty well. If this could be the supported version for Python3, that would be great.
Seeya. Danny. On Wed, 19 Feb 2020 at 12:46, Mike Dewhirst <mi...@dewhirst.com.au> wrote: > Ed > > I really appreciate your work and love Mezzanine and Fabric. > > I would like to see the fabfile kept in Mezzanine and enhanced slightly > by removing repo specifics to make it repo-agnostic. > > I use and support a number of Subversion repos. I have done this for > more than a decade and although I have occasionally tried, I don't have > the brainspace or need for Git (or Hg) as well as svn. Occasionally I'm > forced to use it so I have to resort to googling Git recipes. It isn't > pleasant and I always need a stiff whisky afterwards. > > I once enhanced the fabfile to work with svn and was about to contribute > it back to the project when a new release came out. That meant I needed > to redo the work and I never did find the time to do it again. Since > then I have been muddling along manually and my Mezz work has gradually > diminished. > > I'd be happy to contribute to any svn stuff and test it. > > Cheers > > Mike > > On 19/02/2020 12:16 pm, Eduardo Rivas wrote: > > Hello everyone, > > > > I'm Ed, one of the collaborators helping maintain Mezzanine. As we > > prepare to release the next version of Mezzanine (supporting Python 3 > > and Django 2.2 only) an issue was recently filed > > <https://github.com/stephenmcd/mezzanine/issues/1957> wondering about > > the future of mezzanine's built-in fabfile (which only works with > > Python 2). > > > > This made me wonder: Are Fabric deployments widely used by the > > community? What are your thoughts on the following options: > > > > * Stop maintaining a fabfile of our own and just point people to > > general Django deployment docs > > * Extract the fabfile as a separate package/project > > * Keep the fabfile as part of Mezzanine > > > > Looking forward to hearing from the community. > > -- > > You received this message because you are subscribed to the Google > > Groups "Mezzanine Users" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to mezzanine-users+unsubscr...@googlegroups.com > > <mailto:mezzanine-users+unsubscr...@googlegroups.com>. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/mezzanine-users/02b090b5-2d83-485d-aee3-f5997da14844%40googlegroups.com > > < > https://groups.google.com/d/msgid/mezzanine-users/02b090b5-2d83-485d-aee3-f5997da14844%40googlegroups.com?utm_medium=email&utm_source=footer > >. > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to mezzanine-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/mezzanine-users/ab47f973-5e3d-9c91-5eb8-613279cbd147%40dewhirst.com.au > . > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mezzanine-users/CAKyDYnc2Se%3DnWYOuotzFrAx-Zf1%3D8m7N%3DcXr8r%2BMCtHgyJoRAg%40mail.gmail.com.
