I am following the tdd Django tutorial, i am using python 2.7 and django 1.5
i got error in tutorial 2
Traceback (most recent call last):
File "/usr/lib/python2.7/wsgiref/handlers.py", line 86, in run
self.finish_response()
File "/usr/lib/python2.7/wsgiref/handlers.py", line 127, in
finish
hello friend
i am using pinax(django) for my project in that it contains two
views(signupview/loginview) and having diferent url "account/signup" &
"account/login"
so when i am calling two url in one page(index.html).it's overwritting each
other forms.
plz provide some solution
The unicode error appears to be GroupRegistration but there is *no data* in
that table as yet!
I checked that by rem the inlines in admin.py and separately the grup line in
Register
Caught UnicodeEncodeError while rendering: 'ascii' codec can't encode character
u'\xf6' in position 26:
ordin
The ordinal error is in GroupRegistration becasue if I rem the group line in
Register the admin works BUT there is no data in GroupRegistration so how can I
have this error?
Caught UnicodeEncodeError while rendering: 'ascii' codec can't encode character
u'\xf6' in position 26: ordinal not in
Hi,
I am trying to update Django in OpenBSD ports and I am experiencing a unit
test failure when testing django 1.5.2/1.5.3 on the latest snapshot of
OpenBSD. The failure is with test:
django.contrib.formtools.tests.wizard.wizardtests.tests.WizardFormKwargsOverrideTests.test_instance_is_mainta
Are you reusing an old database or something? There should be only two
users in the database prior to testing that section.
# Create two users so we can filter by is_staff when handing our
# wizard a queryset keyword argument.
self.normal_user = User.objects.create(username='test1',
email='nor..
Hi,
Thank you for responding.
We are using the test_sqlite.py as the settings file for the regression
tests, which I believe should be creating new sqlite databases in memory.
So there shouldn't be any old database files being used.
We are using the same procedure as we did with 1.5.1 and I
Earlier today a message posted to the django-developers mailing list
publicly disclosed what was later determined to be an exploitable security
issue in Django.
As such, we have short-circuited our normal one-week process and moved to
immediately issuing new releases to remedy the problem.
Full d
8 matches
Mail list logo