Re: Django tutorial hasn't received an update for 1.3

On Mon, Oct 31, 2011 at 3:08 PM, Kevin <kveroneau <at> gmail.com> wrote:
> I keep checking the tutorial page for version 1.3 hoping to see some
> new content related to the class-based views or at least some of the
> promised future tutorials.  The tutorial still has the function-based
> views, and no new updates since I first went through it on the 1.2
> release.
>
> I know the function views work in 1.3, but shouldn't the tutorial be
> using the latest features included in 1.3 so that new users coming to
> Django begin learning the newest features, such as class-based views.
>
> I'm still a dinosaur and using Django 1.2 and haven't yet dived into
> class-based views, and when I do, I would love a great tutorial on how
> to proceed.  I plan on learning Django 1.3's newest features very soon
> to keep myself up to speed and see if my current apps are fully
> compatible.
>
> Are there any updates on when we will see the following new tutorial
> sections:

Unfortunately, we can't give you an estimate of when more tutorials
will land -- the only real answer is "when they're written".

One of the embarrasing things about Django's docs is that Tutorial 4
ends with "More tutorials coming soon". It said when *I* started using
Django -- 6 years ago.

This is definitely something that I would like to see addressed;
however, good tutorials are time consuming to write, and nobody has
volunteered to write one (there is a draft for a Tutorial 5 that has

Re: Can't add superuser

Re: I can't activate the admin site

On Mon, 2011-10-31 at 17:31 +0200, Nick Apostolakis wrote:
> On 31/10/2011 02:12 μμ, kenneth gonsalves wrote:
> >
> > but the indentation error seems to be in the django source code?
> > Normally one does not fiddle with that.
> >    
> 
> no I wouldn't expect the indentation problem to be located in django
> code.
> unless you are using an unstable version or something....
> 
> 

the source might have got corrupted. A reinstall may solve the problem.
-- 
regards
Kenneth Gonsalves

--

-- 
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users <at> googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Django - tutorial part 2 problem - Permission denied when attempting to save file

Got this error
Ran into this as part of the Django tutorial (part 2)  very close to
the bottom ....  an attempt to change the page header/title.

"There was an error attempting to save 'base_site.html':Permission
denied"

when trying to save the file below (copied from django source code)

{% extends "admin/base.html" %}
{% load i18n %}

{% block title %}{{ title }} | {% trans 'Django site admin' %}{%
endblock %}

{% block branding %}
<h1 id="site-name">{% trans 'Django administration' %}</h1>
{% endblock %}

{% block nav-global %}{% endblock %}

any thoughts?

--

-- 
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users <at> googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Re: Django - tutorial part 2 problem - Permission denied when attempting to save file

It looks like you don't have write permissions to the "base_site.html"
file, or if the file doesn't exist, than you likely don't have proper
permissions for the enclosing folder. What is the full path of the file
you're attempting to edit?

On 10/31/2011 6:30 PM, BillB1951 wrote:
> Got this error
> Ran into this as part of the Django tutorial (part 2)  very close to
> the bottom ....  an attempt to change the page header/title.
>
>
> "There was an error attempting to save 'base_site.html':Permission
> denied"
>
> when trying to save the file below (copied from django source code)
>
>
>
> {% extends "admin/base.html" %}
> {% load i18n %}
>
> {% block title %}{{ title }} | {% trans 'Django site admin' %}{%
> endblock %}
>
> {% block branding %}
> <h1 id="site-name">{% trans 'Django administration' %}</h1>
> {% endblock %}
>
> {% block nav-global %}{% endblock %}
>
>
> any thoughts?
>

--

-- 
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users <at> googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Re: Why are my two django objects of the same type behaving differently?

Somebody answered this
http://stackoverflow.com/questions/7954474/why-are-my-two-django-objects-of-the-same-type-behaving-differently

 ...
>>> s = '%build%'
>>> content_query = content_class.objects.raw("Select * from pms_building where name like %s",[s])
>>> type(content_query)
<Building: Building A>

Works well.

Thanks

On Oct 31, 5:30 pm, Gath <pgath... <at> gmail.com> wrote:
> Help!
>
> I have two objects that i have created using different techniques in
> django;
>
> >>> from django.contrib.contenttypes.models import ContentType
> >>> from myproject.models import Building
>
> Method A
>
> >>> content_type = ContentType.objects.get(app_label='myproject', model='Building')
> >>> content_class = content_type.model_class()
> >>> content_query = content_class.objects.raw("Select * from pms_building where name like '%build%' ")
> >>> type(content_query)
>
> <class 'django.db.models.query.RawQuerySet'>>>> content_query[0]
>
> # error ....
> # Attribute: 'str' object has no attribute 'items'
>
> Method B
>
> >>> bld = Building.objects.raw("Select * from pms_building where name like '%build%' ")
> >>> type(bld)
>
> <class 'django.db.models.query.RawQuerySet'>
>
> >>>bld[0]
>
> <Building: Building A>
>
> My question is why are the two objects of the same type behaving
> differently?
>
> Gath

--

-- 
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users <at> googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Re: Can't add superuser

On Nov 1, 4:43 am, Karen Tracey <kmtra... <at> gmail.com> wrote:
> On Mon, Oct 31, 2011 at 8:43 AM, rihad <ri... <at> mail.ru> wrote:
> > Hi, I'm unable to add superuser. Running latest development trunk of
> > Django, & Python 2.7
>
> This has been reported:https://code.djangoproject.com/ticket/16017
>
> One way to fix it would be to get a locale properly set on your machine.

Thanks. I just set LANG=en_US.UTF-8 (from empty), dropped the
auth_user & django_site tables for them to be recreated, ran "manage
syncdb", and now everything works. Apparently it's a new quirk of
Django, earlier releases didn't care if LANG was set.

--

-- 
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users <at> googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Re: new formwizard - how to pass data between forms

Set of choices of which several can be chosen without using a ManyToManyField

Hello,

what is the most straightforward way to use a set of choices of which
several can be chosen without using a ManyToManyField?

Using a ManyToManyField would make my program unnecessarily
complicated.

Example:

class Candidate(models.Model):

    programming_languages = models.MultipleChoiceField(max_length=50,
choices=( # replace MultipleChoiceField with existing possibility

            (u'Python)', u'Python'),
            (u'C++', u'C++'),
            (u'Java', u'Java'),
            # ...
            ), blank=True)

Jaroslav

--

-- 
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users <at> googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Disk I/O Error

I'm getting a DatabaseError, looking like this:

Django Version: 	1.3
Exception Type: 	DatabaseError
Exception Value: 	disk I/O error
Exception Location: 	/usr/local/lib/python2.6/dist-packages/django/db/
backends/sqlite3/base.py in execute, line 234

whenever I try to read or write to any of the databases associated
with any of the websites on one of our servers. The fact that all
these websites work locally, but not in their live versions seems to
suggest to me that something has gone wrong on the server, rather than
with django, but I thought I'd better ask and see if any one has had
any similar issues. I'm running python 2.6.6, django 1.3 and they're
on a Linux server.

--

-- 
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users <at> googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.