Re: 'fabric1' and 'fabric2' packages

2020-06-15 Thread Jeff Forcier
> > 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

Re: 'fabric1' and 'fabric2' packages

2020-06-04 Thread za3k--- via
On 2020-05-29 06:14, Jeff Forcier wrote: This class of issue is a longstanding rare-but-never-vanquished frustration with Paramiko. I'd definitely make sure the Paramiko version is a recent (re: list of releases; I have not put any out in the last N months...) release. Well, I was able to

Re: 'fabric1' and 'fabric2' packages

2020-05-29 Thread Jeff Forcier
> > OK, well some small updates. > - Debian has indeed closed the door on new python2 packages, trying to > eliminate python2 from their ship stack altogether > Not unexpected, but thanks anyway for asking them! > - Arch doesn't seem to have any problem with it, but the default install > for

Re: 'fabric1' and 'fabric2' packages

2020-05-27 Thread za3k--- via
- I think it's worth asking the distros if they would allow a Python 2 Fabric 1 option, for those users who are still stuck supporting Py2, but like you say I would not be surprised if they've already closed that door. Will do. I'll hand them a package and they can say yes or no (asking before

Re: 'fabric1' and 'fabric2' packages

2020-05-26 Thread za3k--- via
+mailing list On 2020-05-25 15:19, z...@za3k.com wrote: On 2020-05-25 12:40, Jeff Forcier wrote: - First, please understand I'm still kinda buried so I can't take any serious action on my end this week. Hopefully by June. No worries, I'm currently retired after like 3 consecutive startup jobs

Re: 'fabric1' and 'fabric2' packages

2020-05-26 Thread za3k--- via
+mailing list, accidentally replied to Jeff/bitprophet directly On 2020-05-24 16:39, z...@za3k.com wrote: Thanks for the info, you're encouraging me. FYI my timeline is something like "this week", I don't see any big chunks of coding needed. 1. I see a couple options at this point. I'm going

Re: 'fabric1' and 'fabric2' packages

2020-05-26 Thread za3k--- via
+mailing list, accidentally replied to Jeff/bitprophet directly On 2020-05-25 12:40, Jeff Forcier wrote: In rough order: - First, please understand I'm still kinda buried so I can't take any serious action on my end this week. Hopefully by June. - FYI, my schedule at the dayjob is "open

Re: 'fabric1' and 'fabric2' packages

2020-05-23 Thread Jeff Forcier
I'm still digging myself out of a couple large 2019/2020 related personal holes (and that was all before The Circumstances happened), but this sort of thing has been on my mind lately (blog post forthcoming). Thanks for reaching out about it - lots of folks seem to think that just dropping a

Re: 'fabric1' and 'fabric2' packages

2020-05-23 Thread za3k--- via
Hmm okay, so Python2 end-of-life was Jan 1. So actually, I think I will offer to backport python3 support to Fabric 1.x. This one I'm going to wait on a 'yes' before starting.