--- Begin Message ---
Subject: |
Certbot with Python 3 |
Date: |
Sun, 7 May 2017 14:46:10 -0400 |
User-agent: |
Mutt/1.8.2 (2017-04-18) |
The latest release of Certbot and the acme library can use Python 3 [0].
These patches create a new address@hidden variable, and then upgrade
certbot and python-acme to use Python 3 by default. I did some light
testing by renewing some certificates.
[0]
https://github.com/certbot/certbot/pull/4568/commits/48b47274e7e6b11b7748b72a8e87add3f218e8b7
0001-gnu-Add-python-mock-2.patch
Description: Text document
0002-gnu-certbot-Build-with-Python-3.patch
Description: Text document
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#26818: Certbot with Python 3 |
Date: |
Mon, 19 Jun 2017 13:08:00 -0400 |
User-agent: |
Mutt/1.8.3 (2017-05-23) |
On Sun, Jun 18, 2017 at 01:10:38PM +0200, Ricardo Wurmus wrote:
>
> Hi Leo,
>
> > The latest release of Certbot and the acme library can use Python 3 [0].
> >
> > These patches create a new address@hidden variable, and then upgrade
> > certbot and python-acme to use Python 3 by default. I did some light
> > testing by renewing some certificates.
> >
> […]
> > Subject: [PATCH 1/2] gnu: Add python-mock-2.
> > Subject: [PATCH 2/2] gnu: certbot: Build with Python 3.
> […]
>
> Is there something holding up merging these patches? I haven’t seen
> them in master nor in core-updates.
I'd hoped to hear about some other people testing this Python-3 certbot,
but since it's working for me, I pushed as
fed1898d4e7855de03a276eb4d370ca1d32a789e.
Thanks for the reminder!
signature.asc
Description: PGP signature
--- End Message ---