On Wed, Feb 7, 2018 at 11:54 AM Kenneth Porter <sh...@sewingwitch.com> wrote:
> --On Wednesday, February 07, 2018 9:35 AM -0800 Kenneth Porter > <sh...@sewingwitch.com> wrote: > > > So there's a builtins package hiding in this system somewhere. > > Found it. The system has the python2-future package which is a dependency > of the certbot package. I think I got that from the epel repo. > > Here's the metadata for that package: > > rpm -qi python2-future > Name : python2-future > Version : 0.16.0 > Release : 6.el7 > Architecture: noarch > Install Date: Sun Jan 7 21:05:17 2018 > Group : Applications/Engineering > Size : 3796094 > License : MIT > Signature : RSA/SHA256, Fri Dec 15 05:27:05 2017, Key ID 6a2faea2352c64e5 > Source RPM : future-0.16.0-6.el7.src.rpm > Build Date : Fri Dec 15 05:24:22 2017 > Build Host : buildvm-aarch64-18.arm.fedoraproject.org > Relocations : (not relocatable) > Packager : Fedora Project > Vendor : Fedora Project > URL : http://python-future.org/ > Summary : Easy, clean, reliable Python 2/3 compatibility > Description : > Python2 future is the missing compatibility layer between Python 2 and > Python 3. It allows you to use a single, clean Python 3.x-compatible > codebase to support both Python 2 and Python 3 with minimal overhead. > > It provides ``future`` and ``past`` packages with backports and forward > ports of features from Python 3 and 2. It also comes with ``futurize`` and > ``pasteurize``, customized 2to3-based scripts that helps you to convert > either Py2 or Py3 code easily to support both Python 2 and 3 in a single > clean Py3-style codebase, module by module. > > If that package was being imported, I'd definitely expect that kind of behavior, but merely it's presence on your system should not be enough to actually cause your python scripts to use the "future" behavior within python 2.7. Has the mailer.py been changed, or is it being imported by some other script as a module that does import the future module? Troy
