Hi,
Konstantin Khomoutov:
> have discovered the tests attempt to connect to a MySQL instance on
> the localhost, and authenticate there as the user "root" using no
> password.
I would file an Upstream bug for this. They should use a "test" user with a
"test_PACKAGENAME" database, and make the mys
Hi,
I'm trying to upgrade dicompyler[1] but I seem to have some final
problem:
$ dicompyler
Traceback (most recent call last):
File "/usr/share/dicompyler/dicompyler_app.py", line 10, in
import dicompyler.main
File "/usr/share/dicompyler/__init__.py", line 10, in
from main import st
[Andreas Tille, 2014-09-10]
> BTW, as I previously wrote here on this list[2] I'm afraid I did not
> found a clever solution to package this Python application. I learned
> here on this list that applications should go to /usr/share/
> but I needed to set PYTHONPATH in a wrapper to make this worki
[Piotr Ożarowski, 2014-09-10]
> all you need is `dh_link /usr/bin/foo /usr/share/pkgname/foo` in
or even `dh_link /usr/share/pkgname/foo /usr/bin/foo` :)
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fi
On 9 September 2014 09:28, Piotr Ożarowski wrote:
> (I will remove all .../dist-packages/test{,s} by default in next
> dh_python{2,3} version).
Does this mean we'll get a nice warning too, so we know that we need
to report the bug upstream? :)
♥,
- Tianon
--
To UNSUBSCRIBE, email to debian-pyt
Hi Piotr,
On Wed, Sep 10, 2014 at 04:03:40PM +0200, Piotr Ożarowski wrote:
>
> if you install your script to the same directory as the application¹ then
> all you need is `dh_link /usr/bin/foo /usr/share/pkgname/foo` in
> debian/rules or adequate line in debian/pkgname.links file.
> No need to wr
[Andreas Tille, 2014-09-10]
> Copying dicompyler.egg-info to
> /tmp/buildd/dicompyler-0.4.2/debian/dicompyler/usr/share/dicompyler/dicompyler-0.4.2.egg-info
> running install_scripts
> Installing dicompyler script to
> /tmp/buildd/dicompyler-0.4.2/debian/dicompyler/usr/share/dicompyler
> error: [
[Tianon Gravi, 2014-09-10]
> On 9 September 2014 09:28, Piotr Ożarowski wrote:
> > (I will remove all .../dist-packages/test{,s} by default in next
> > dh_python{2,3} version).
>
> Does this mean we'll get a nice warning too, so we know that we need
> to report the bug upstream? :)
yes (and I'm
On 10 September 2014 11:11, Piotr Ożarowski wrote:
> yes (and I'm still wondering if failing with an error message that this
> module name is too generic is a better idea)
I'd personally love to see it hard fail (since warnings will be quite
often missed), especially if it included some hints abo
The mathplotlib API changes document recommends switching from
matplotlib.nxutils to matplotlib.path.Path.contains_point and friends.
http://matplotlib.org/api/api_changes.html#id1
Also I used codesearch.d.n and found some code which supports both
versions of the mathplotlib API:
http://sources.
On 7 August 2014 10:19, Brian May wrote:
> virtualenv --system-site-packages ~/old_django
> . ~/old_django/bin/activate
> pip install django==1.6.5
> pip install django-south
> django-admin --settings=??? migrate --all
>
Calling django-admin like that won't use the virtualenv.
> touch /etc/xyz
Hi Brian,
thanks for those investigations!
On Thu, 11 Sep 2014, Brian May wrote:
> Note that I have explicitly called python. This ensures Python 3 not used
> (not supported by South + the virtualenv is Python 2 only) and that we get
> the python from the virtualenv.
>
> I have tested this and i
On 11 September 2014 16:28, Raphael Hertzog wrote:
> Please document this in python-django's README.Debian and mention where to
> find this sample in the current debian/python-django.NEWS entry.
>
Ok, will look into this tomorrow.
Also noticed that /usr/bin/django-admin has Python 2.6 stuff tha
13 matches
Mail list logo
