Mailinglist Archive: opensuse-packaging (267 mails)
| < Previous | Next > |
Re: [opensuse-packaging] Python 2 and Python 3 compatibility packaging
- From: Claudio Freire <klaussfreire@xxxxxxxxx>
- Date: Mon, 5 Dec 2011 18:31:25 -0300
- Message-id: <CAGTBQpYBmRfh1G8tdN9poMwtJYv5ay2mPCYYVoVpmTi7qz1C+g@mail.gmail.com>
On Mon, Dec 5, 2011 at 6:27 PM, todd rme <toddrme2178@xxxxxxxxx> wrote:
Somehow, I don't see your problem.
Can you point to an OBS project that fails because of that?
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx
I am talking about things currently installed in /usr/bin and
/usr/share, so what python calls scripts and data, respectively. libs
are not a problem because they are already in a versioned directory.
Then your above point is moot.
A python3 lib/app can only "look for" other python3 libs. Not apps
(scripts).
If a python3 lib *executes* another python app, it doesn't care if
it's python3 or python2, as long as it's the same app.
That is only true if the scripts are identical between the python 2
and python 3 versions. That may be the case but you can't assume it.
Sorry to double (or triple) post, but even if the scripts are
identical, it still doesn't really solve the issue because we still
have duplicates that need to be dealt with somehow.
Somehow, I don't see your problem.
Can you point to an OBS project that fails because of that?
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx
| < Previous | Next > |