I've been seeing this same exact issue, even after completely deleting
and re-exporting Django and my project's source (minus all .pyc
files). It appears to be something else that's being buried by that
non-descriptive error message.
On Oct 1, 2:53 pm, hotani <[EMAIL PROTECTED]> wrote:
> It's bac
I just got bit by this too and it turned out that I had done an
install of Django-1.0 on top of an older Django install. In the site-
packages directory there was both a django/contrib/comments/urls.py
(from 1.0) and a django/contrib/comments/urls/ directory which
contained __init__.py and comment
It's back!
No error on dev server, but crashing like crazy on test with same old
crap:
>> Caught an exception while rendering: Reverse for '> 0x2ae96d979410>' with arguments '()' and keyword arguments '{}' not found
It alternates between that and:
>> Caught an exception while rendering: No modul
On Sep 17, 7:01 am, Jarek Zgoda <[EMAIL PROTECTED]> wrote:
> Wiadomość napisana w dniu 2008-09-16, o godz. 19:31, przez Mark:
>
> > I tried everything:
> > - Deleted django/contrib/comments*.pyc files (a number of times)
> > - updated to svn latest (a number of times :) )
>
> That's not "everyth
Wiadomość napisana w dniu 2008-09-16, o godz. 19:31, przez Mark:
> I tried everything:
> - Deleted django/contrib/comments*.pyc files (a number of times)
> - updated to svn latest (a number of times :) )
That's not "everything" ;). Doing rm -rf django/contrib/comments was
the thing I did. And
If it's any consolation, I've had the the same bugs. I kept getting
the same reverse lookup function error whenever I tried to render the
comments form. I looked through all my comments directories, and
deleted all .pyc files. I finally got rid of all my reverse()
problems after I searched my e
Hi,
Finally - I got comments to work - but not correctly :-(
Django version - svn:9003
Urls conf ..
(r'^comments/', include('django.contrib.comments.urls')),
I tried everything:
- Deleted django/contrib/comments*.pyc files (a number of times)
- updated to svn latest (a number of times :)
zapped django from site-packeges, updated to 8797 but still have this
error. Running the django/test over a fresh checkout got a lot of
fails on comments contrib app.
es
ERROR: testRenderCommentFormFromLiteral
(regressiontests.comment_tests.tests.templatetag_tests.CommentTemplateTagTests)
-
...and of course, I find that http://code.djangoproject.com/ticket/8221
is now fixed!
That should help clear up an awful lot of confusion.
As of r8672, it's in the trunk.
Cheers,
Tone
On Aug 29, 7:40 am, tonemcd <[EMAIL PROTECTED]> wrote:
> Also
> seehttp://groups.google.com/group/django-user
Also see
http://groups.google.com/group/django-users/browse_thread/thread/1f4bb991f9f0f7b5/62005ad4330c4884?lnk=gst&q=noReverseMatch#62005ad4330c4884
Short summary: maybe your named url regexes aren't matching the
variables passed to them in the {% url ... %} tag.
Apply the patch from http://cod
Did you delete the .pyc files from the django source? Another approach
would be to go into /django/contrib/ and delete the comments
directory, then do an 'svn up' to restore it. Then you'll be sure to
get a fresh copy.
That is what worked for me. But if you haven't used the comment system
before
Hi,
Updated to 8613 with the release of Django 1.0 Beta 2 and saw the
addition of commenting framework - tried to add it and am getting a
similar error to above.
On Aug 27, 3:54 pm, Slavus <[EMAIL PROTECTED]> wrote:
> Here is the solution:
> You'll get this if you still have stale pyc files left
Here is the solution:
You'll get this if you still have stale pyc files left over from the
old comment system. Delete 'em and your code will work.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
Well it happened again when I uploaded the comment changes to another
server.
Here's the fix: go to /django/contrib/comments and wipe out the .pyc
files:
sudo rm */*.pyc
that finally fixed it.
On Aug 26, 11:37 am, hotani <[EMAIL PROTECTED]> wrote:
> This ended up working (I honestly don't rem
This ended up working (I honestly don't remember which tinker finally
did it...):
{% render_comment_form for object %}
I also had to make an additional change in urls:
old way="django.contrib.comments.urls.comments"
new="django.contrib.comments.urls"
At least things are showing up now and not ex
No idea. I seem to be getting the same thing.
The comments upgrade has caused all kinds of meltdowns in my
applications. For one, updating the SQL failed. PostgreSQL was
complaining because it was updating fields set to "NOT NULL" with null
values. I changed the query to accommodate for this, now
16 matches
Mail list logo
