Hi Malcom,
and thanks for your answer.
On Jul 3, 8:37 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> Not knowing anything about this particular project, but if that's what
> the line really says in the source (and I'm not doubting you, just very
> surprised), it's completely wrong. It's
On Wed, 2008-07-02 at 23:18 -0700, Ulf Kronman wrote:
> Hi again all,
> after a few days of struggling with django-pyodbc, I have finally got
> past the "ImportError: No module named django-pyodbc.db.mssql.base"
> stage.
>
> The problem was that the module package was missing __init__.py files
Hi again all,
after a few days of struggling with django-pyodbc, I have finally got
past the "ImportError: No module named django-pyodbc.db.mssql.base"
stage.
The problem was that the module package was missing __init__.py files
in the directories above the mssql directory. So I added two empty
[Posted this reply yesterday, but I can't see it, I post it again.
Sorry for any duplication. / Ulf ]
On Jun 27, 4:12 pm, gordyt <[EMAIL PROTECTED]> wrote:
> Ulf I haven't played with this second solution, but I did just check
> out a copy of the django-pyodbc project. You should be OK
Ulf I haven't played with this second solution, but I did just check
out a copy of the django-pyodbc project. You should be OK following
the author's instructions. He said to add the django-pydobc directory
(where ever you choose to put it) to your PYTHONPATH. The name of the
module(s) that
Hi all,
sorry; I know that this is an ever-coming-back question, but I need to
dig a bit deeper to get further, before deciding to struggle on or
give up.
I've been coding happily with Django for over a year, using an Ubuntu
server with a PostgreSQL database and a development environment on Max
6 matches
Mail list logo
