Re: django.contrib.markup and ReST

[sorry if this message appeared second time] > This is intended behavior from docutils: if the reST document starts > with a header it is considered the "document header" and is > intentionally not a part of the fragment by default. Rather than > using the body the correct approach would be to

project folder with dots

Hello, django developers! On my server every project has it's own folder which name is the same as project hostname(ex. /home/testsite.com). Bug django don't allow dots in "project name". I think we can fix it. For example by avoiding starting import with project name.

Re: project folder with dots

> IMHO the project namespace is a useful one to keep around. If you > lose the project name space, then you risk polluting your python path > with a lot of generic 'urls' modules, among other things. I don't understand why in tutorial all imports contain project name. I think this is wrong

Re: project folder with dots

> To fix the code is easy enough. But to update all of the relevant > documentation and to require all existing Django deployments to have > to migrate their project structures (or change all of their imports) > to upgrade is a much bigger issue to tackle. Thank you for answer. Do you think it's

Re: How do I tap into admin.py to generate data from models?

On Sun, 29 Nov 2009 09:42:23 -0800 (PST) Joshua Kramer wrote: > > I am currently modeling the SQL creation code in sql.py and > creation.py, as well as the field type code in fields.py. So I'm on a > good track - now where should I look to hook into admin.py? Override

Re: Running unit tests when you can't create a new database

> Django allows you to define a custom test runner. Copy > django.tests.simple.run_tests() into your own code, removing the calls > to create and destroy the test database. Then set TEST_RUNNER in your > settings file to point at the new runner. Hello! I see many similar bugreports and wishes

Re: Django 1.2 progress assessment

> So the question is: given what we've got done, and guess at what we > will get done, is the current timeline still feasible, or should we > push the timeline? As I understood logging support for django is complete now. Or not? -- You received this message because you are subscribed to the

Re: Templates by app

You can use both schemes. > Is there any reason to have a global directory with all templates > instead of to have the templates for each application: > > project/ > \___ apps/ > \___ templates/ > -- You received this message because you are subscribed to the Google Groups "Django

Re: Decision required: PostgreSQL minimum versions

For old postgress we have old django. So, do not hesitate kicking off old code. Even 8.2 version is very-very old so it's okay to depend on 8.2+. > While we support PostgreSQL, our documentation doesn't actually > specify a minimum supported version. We have a couple of features that > are no-ops

Re: ModelView

> Anybody likes the idea? Sounds good. Unfortunately I didn't read long-long thread about class-based views :( > - I'm no fan of 'class Meta' myself, but I've chosen it here to be > compatible with ModelForm I'm too -- You received this message because you are subscribed to the Google Groups