Hi Barry,
I updated Python 2.7 to experimental and rebuild python-virtualenv with the
multiarch patch. Now that works.
But I add to delete and re-create my virtual environment (sorry, I did not
note down the error message / problem). Maybe this worth an entry in the
readme / changelog / news.
Alioth svn updated with latest patch based on comments in bug #695958. Once
that gets uploaded, then svn can get sponsored to fix the problem.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Am 12.12.2012 21:06, schrieb Barry Warsaw:
Or this one...
when creating a virtualenv, you usually know which interpreter you'll be using
for the new env, so why not use the interpreter to get the name of the dir?
python -S -c 'import sys, os.path; print [os.path.basename(d) for d in sys.path
if
On Dec 13, 2012, at 11:04 AM, Matthias Klose wrote:
Am 12.12.2012 21:06, schrieb Barry Warsaw:
Or this one...
when creating a virtualenv, you usually know which interpreter you'll be
using for the new env, so why not use the interpreter to get the name of the
dir?
python -S -c 'import sys,
How horrible is it to use dpkg-architecture? It adds a dependency on
dpkg-dev, but that doesn't seem so bad to *me*. :)
Attached is a patch that uses dpkg-architecture and fixes the problem for me.
=== modified file 'debian/changelog'
--- debian/changelog 2012-11-30 15:06:23 +
+++
Or this one...
=== modified file 'debian/changelog'
--- debian/changelog 2012-11-30 15:06:23 +
+++ debian/changelog 2012-12-12 19:11:43 +
@@ -1,3 +1,10 @@
+python-virtualenv (1.8.4-2) experimental; urgency=low
+
+ * debian/patches/multiarch.patch: Use system multiarch path if available.
+
6 matches
Mail list logo
