[Avocado-devel] Heads-up: dropping Python 2.6 support

Tue Feb 7 15:10:06 UTC 2017

Ok. Thank you.

For your information there is some warning about wheel.

However, it works even with this warning.

# pip install 'avocado-framework==36.0'
DEPRECATION: Python 2.6 is no longer supported by the Python core team,
please upgrade your Python. A future version of pip will drop support for
Python 2.6
Collecting avocado-framework==36.0
/root/a1/lib/python2.6/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:318:
SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject
Name Indication) extension to TLS is not available on this platform. This
may cause the server to present an incorrect TLS certificate, which can
cause validation failures. You can upgrade to a newer version of Python to
solve this. For more information, see
https://urllib3.readthedocs.io/en/latest/security.html#snimissingwarning.
  SNIMissingWarning
/root/a1/lib/python2.6/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:122:
InsecurePlatformWarning: A true SSLContext object is not available. This
prevents urllib3 from configuring SSL appropriately and may cause certain
SSL connections to fail. You can upgrade to a newer version of Python to
solve this. For more information, see
https://urllib3.readthedocs.io/en/latest/security.html#insecureplatformwarning
.
  InsecurePlatformWarning
  Downloading avocado-framework-36.0.tar.gz (714kB)
    100% |████████████████████████████████| 716kB 1.4MB/s
  Running setup.py (path:/tmp/pip-build-7Ia2vz/avocado-framework/setup.py)
egg_info for package avocado-framework produced metadata for project name
avocado. Fix your #egg=avocado-framework fragments.
Building wheels for collected packages: avocado, avocado
  Running setup.py bdist_wheel for avocado ... done
  Stored in directory:
/root/.cache/pip/wheels/6a/20/35/aa577931e4582057dbee3fd3250636ef75e7d5e503e98e5249
  Running setup.py bdist_wheel for avocado ... error
  Complete output from command /root/a1/bin/python -u -c "import
setuptools,
tokenize;__file__='/tmp/pip-build-7Ia2vz/avocado/setup.py';f=getattr(tokenize,
'open', open)(__file__);code=f.read().replace('\r\n',
'\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d
/tmp/tmpX7VmYGpip-wheel- --python-tag cp26:
  Traceback (most recent call last):
    File "<string>", line 1, in <module>
  IOError: [Errno 2] No such file or directory:
'/tmp/pip-build-7Ia2vz/avocado/setup.py'

  ----------------------------------------
  Failed building wheel for avocado
  Running setup.py clean for avocado
  Complete output from command /root/a1/bin/python -u -c "import
setuptools,
tokenize;__file__='/tmp/pip-build-7Ia2vz/avocado/setup.py';f=getattr(tokenize,
'open', open)(__file__);code=f.read().replace('\r\n',
'\n');f.close();exec(compile(code, __file__, 'exec'))" clean --all:
  Traceback (most recent call last):
    File "<string>", line 1, in <module>
  IOError: [Errno 2] No such file or directory:
'/tmp/pip-build-7Ia2vz/avocado/setup.py'

  ----------------------------------------
  Failed cleaning build dir for avocado
Successfully built avocado
Failed to build avocado
Installing collected packages: avocado
Successfully installed avocado-36.0lts

On Tue, Feb 7, 2017 at 4:06 PM, Cleber Rosa <crosa at redhat.com> wrote:

>
> On 02/07/2017 09:53 AM, Andrei Stepanov wrote:
> > It seems that I can install: Avocado LTS using virtualenv + avocado-vt
> > from github as a plugin.
> >
> > avocado shows tp-qemu tests.
> >
> > My steps are:
> >
> > 1. Enable RHEL optional repo.
> > 2. yum install libvirt libvirt-devel xz-devel libffi-devel python-devel
> > openssl-devel openssl-devel "@Development tools"
> > 3. python get-pip.py --user
> > 4. ./.local/bin/pip install --user virtualenv
> > 5. ./.local/bin/virtualenv a1
> > 6. . ./a1/bin/activate
> > 7. pip install -r
> > https://raw.githubusercontent.com/avocado-framework/avocado/
> 36lts/requirements.txt
> > 8. pip install 'avocado-framework==36.0'
> > 9. pip install aexpect netaddr autotest
> > 10. pip install -e
> > "git+git://github.com/avocado-framework/avocado-vt#egg=
> avocado-plugins-vt <http://github.com/avocado-framework/avocado-vt#egg=
> avocado-plugins-vt>"
> > 11. yum install yum install p7zip p7zip-plugins  # From EPEL  (can we
> > get away from p7zip ?)
> > 12. yum install qemu-kvm qemu-kvm-tools
> > 13. avocado vt-bootstrap --vt-no-downloads
> > 14. avocado list
> >
> > How do you think, is this right approach to use avocado + avocado-vt  on
> > RHEL 6.x + RHEL 7.x?
> >
> >
>
> If it works (as you verified), then it's definitely (one) correct
> deployment scenario.
>
> If you find minor changes that can greatly improve deployment (such as
> changes to requirements.txt), we can consider them "installation bugs"
> and include them in future LTS releases.
>
> - Cleber.
>
> > On Tue, Feb 7, 2017 at 2:41 PM, Cleber Rosa <crosa at redhat.com
> > <mailto:crosa at redhat.com>> wrote:
> >
> >
> >
> >     On 02/07/2017 08:34 AM, Andrei Stepanov wrote:
> >     >
> >     >
> >     > On Tue, Feb 7, 2017 at 2:20 PM, Cleber Rosa <crosa at redhat.com
> <mailto:crosa at redhat.com>
> >     > <mailto:crosa at redhat.com <mailto:crosa at redhat.com>>> wrote:
> >     >
> >     >
> >     >
> >     >
> >     >     Andrei,
> >     >
> >     >     Running a command such as:
> >     >
> >     >     pip install -r
> >     >     https://raw.githubusercontent.com/avocado-framework/avocado/
> 36lts/requirements.txt
> >     <https://raw.githubusercontent.com/avocado-framework/avocado/36lts/
> requirements.txt>
> >     >     <https://raw.githubusercontent.com/avocado-
> framework/avocado/36lts/requirements.txt
> >     <https://raw.githubusercontent.com/avocado-framework/avocado/36lts/
> requirements.txt>>
> >     >
> >     >     Would have probably saved you a lot of this hassle.  This is
> documented
> >     >     here:
> >     >
> >     >     http://avocado-framework.readthedocs.io/en/45.0/
> GetStartedGuide.html#installing-from-standard-python-tools
> >     <http://avocado-framework.readthedocs.io/en/45.0/
> GetStartedGuide.html#installing-from-standard-python-tools>
> >     >     <http://avocado-framework.readthedocs.io/en/45.0/
> GetStartedGuide.html#installing-from-standard-python-tools
> >     <http://avocado-framework.readthedocs.io/en/45.0/
> GetStartedGuide.html#installing-from-standard-python-tools>>
> >     >
> >     >
> >     >
> >     >
> >     > Can I ask why we do not specify required packages for pip?
> >     > http://python-packaging.readthedocs.io/en/latest/dependencies.html
> >     <http://python-packaging.readthedocs.io/en/latest/dependencies.html>
> >     >
> >
> >     We do specify the most basic requirements (stevedore) on newer
> versions,
> >     it did not make into 36lts though.  We can still improve it and
> release
> >     a new 36.x version.
> >
> >     But, even with `install_requires`, some older versions of setuptools
> do
> >     not allow versions to be specified there, which would cause breakage.
> >
> >     Then, there's the question of too many deps required by some plugins,
> >     such as remote (requires fabric), vm (requires libvirt).  We decided
> to
> >     keep the list short and plugins just won't work without the extra
> deps.
> >
> >     You may have noticed that we're working on splitting those plugins
> that
> >     bring extra deps out of the "core" of Avocado:
> >
> >     https://github.com/avocado-framework/avocado/pull/1751
> >     <https://github.com/avocado-framework/avocado/pull/1751>
> >
> >     > It would be fine if next command install all dependency
> automatically:
> >     > pip install 'avocado-framework==36.0'
> >     >
> >     >
> >
> >     It *would* be awesome.  But as you might imagine, it is not *that*
> >     simple.  Putting a `install_requires` and releasing a new 36.x (36.4
> >     now) would be the first big improvement IMHO.
> >
> >     --
> >     Cleber Rosa
> >     [ Sr Software Engineer - Virtualization Team - Red Hat ]
> >     [ Avocado Test Framework - avocado-framework.github.io
> >     <http://avocado-framework.github.io> ]
> >
> >
>
> --
> Cleber Rosa
> [ Sr Software Engineer - Virtualization Team - Red Hat ]
> [ Avocado Test Framework - avocado-framework.github.io ]
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/avocado-devel/attachments/20170207/1191b2eb/attachment.htm>