← Back to team overview

ius-coredev team mailing list archive

[Bug 1356007] Re: python34u pyvenv error

 

As your error output indicated, this is caused because the bundled
setuptools wheel was missing.  Red Hat explicitly strips that out [1],
and adds support for rewheel [2][3].  To resolve this, we need python34u
versions of pip and wheel.  I've got those built, and they will appear
in the testing repos tonight.  I'm working through the python34u spec
file to integrate them properly.  I'll keep you posted.

[1] http://pkgs.fedoraproject.org/cgit/python3.git/commit/?id=cb97d2916653265a7d7a033b14f406d9031a772a
[2] https://github.com/bkabrda/rewheel
[3] http://pkgs.fedoraproject.org/cgit/python3.git/commit/?id=11fb599edb14569b903abafeed7fd2349d96dfbf

** Tags added: python34u

-- 
You received this bug notification because you are a member of IUS Core
Development, which is subscribed to IUS Community Project.
https://bugs.launchpad.net/bugs/1356007

Title:
  python34u pyvenv error

Status in IUS Community Project:
  New

Bug description:
  Breaking this issue off from a separate bug thread.

  https://bugs.launchpad.net/ius/+bug/1301618

  ==========================================================
  hurie (hurie83) wrote on 2014-08-11:

  I got some error when I use pyvenv

  [vagrant@ppdb-vagrant ~]$ pyvenv test
  Error: Command '['/home/vagrant/test/bin/python3.4', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1

  And here the exception when I execute command directly

  [vagrant@ppdb-vagrant ~]$ /home/vagrant/test/bin/python3.4 -Im ensurepip --upgrade --default-pip
  Traceback (most recent call last):
    File "/usr/lib64/python3.4/runpy.py", line 170, in _run_module_as_main
      "__main__", mod_spec)
    File "/usr/lib64/python3.4/runpy.py", line 85, in _run_code
      exec(code, run_globals)
    File "/usr/lib64/python3.4/ensurepip/__main__.py", line 4, in <module>
      ensurepip._main()
    File "/usr/lib64/python3.4/ensurepip/__init__.py", line 209, in _main
      default_pip=args.default_pip,
    File "/usr/lib64/python3.4/ensurepip/__init__.py", line 98, in bootstrap
      "_bundled/{}".format(wheel_name),
    File "/usr/lib64/python3.4/pkgutil.py", line 627, in get_data
      return loader.get_data(resource_name)
    File "<frozen importlib._bootstrap>", line 1623, in get_data
  FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib64/python3.4/ensurepip/_bundled/setuptools-2.1-py2.py3-none-any.whl'

  Also is there any change to install both python33 and python34, there
  some conflict when I try:

  [vagrant@ppdb-vagrant ~]$ sudo yum install python33
  Loaded plugins: fastestmirror
  Loading mirror speeds from cached hostfile
   * epel: mirror.orion.net.id
   * ius: hkg.mirror.rackspace.com
  Setting up Install Process
  Resolving Dependencies
  --> Running transaction check
  ---> Package python33.x86_64 0:3.3.5-2.ius.centos6 will be installed
  --> Processing Dependency: python33-libs(x86-64) = 3.3.5-2.ius.centos6 for package: python33-3.3.5-2.ius.centos6.x86_64
  --> Processing Dependency: libpython3.3m.so.1.0()(64bit) for package: python33-3.3.5-2.ius.centos6.x86_64
  --> Running transaction check
  ---> Package python33-libs.x86_64 0:3.3.5-2.ius.centos6 will be installed
  --> Processing Conflict: python34u-3.4.1-2.ius.centos6.x86_64 conflicts python33
  --> Finished Dependency Resolution
  Error: python34u conflicts with python33-3.3.5-2.ius.centos6.x86_64
   You could try using --skip-broken to work around the problem
   You could try running: rpm -Va --nofiles --nodigest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ius/+bug/1356007/+subscriptions


References