ius-coredev team mailing list archive

[bharper <1356007@xxxxxxxxxxxxxxxxxx>]

Hello Hurie,

Thanks for taking the time to test this fix.  I am glad to hear that
pyvenv is no longer throwing an error.  I will go ahead and push these
updated packages into the stable repo during our nightly automation run.

-Ben

** Changed in: ius
       Status: Fix Committed => Fix Released

-- 
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:
  Fix Released

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