Bug #7504
closed
Ceph does not specify python2
Added by Alexandre BIQUE about 10 years ago.
Updated about 10 years ago.
Description
Hi,
Ceph fails on archlinux because it uses python and not python2.
On Archlinux, python = python3 and to use python2 you must explicitly use python2.
Can you please fix ceph and its related tools like ceph-deploy to use explicitly python2?
Thanks a lot!
- Assignee set to Alfredo Deza
- Priority changed from High to Normal
- Target version deleted (
v0.77)
- Estimated time deleted (
1:00 h)
- Source changed from other to Community (user)
- Severity changed from 2 - major to 4 - irritation
When you say that ceph scripts should 'use explicitly python2' you mean altering the shebang line?
There is no convention around Python versions that would allow scripts to work correctly by attempting to specify it like that.
That means that making it explicit would fix it for Archlinux but would break pretty much everywhere else.
For example '#!/usr/bin/env python2' does not exist in Debian.
The solution (until Ceph scripts support Python3) is to activate/source a virtualenv that is mapped to Python2 when using Ceph scripts.
- Status changed from New to Rejected
Yeah I was talking about the shebang.
I understand that you can't do anything but this situation sucks. Instead of doing things like they should be done: specify python version in the shebang, you're doing bad things to not break old and deprecated systems. It is not complicated to have /usr/bin/python23 on your system. Ensuring that an env is sourced before calling your scripts is something much more complicated.
Anyway thanks.
Also available in: Atom
PDF