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 pass in the proper > flag to disable "document headers" so that the opening. But even "" headers doesn't shown. I think this default behavior is not good as you can't insert any header into your document. Or I missed something? > Rather than switch to the 'html_body', it probably makes more sense > for Django's default template tag to open up a setting to provide > additional flags to publish_parts/docutils writer/docutils > transformer, such as the aforementioned one to disable document > headers, or other generally useful flags such as the ones to enable > certain security features. Thank you for advice, I missed this. At least it will allow me run my site on unmodified django. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
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. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
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 position. In my case I've got one project named "engine" and three sites using it. If I used import containig "engine" I would place every site into the folder with the same name, but it's inconvenient(I think). My idea is to view site as a number of apps. Each app separated from others and keeps anything it needs in its own namespace. What do you think about it? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
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 a good change of django(for ex. for very future versions) or better leave as it is? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
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 save_model in ModelAdmin or create a custom model's save() method. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
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 which was closed with this proposal. Unfortunately this will not work with recent django versions. Errors like AttributeError: 'Settings' object has no attribute 'DATABASE_SUPPORTS_TRANSACTIONS' Please help solving this issue. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
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 Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
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 developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
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 for versions prior to 8.2 (savepoints and database > autocommit), but we don't actually document a minimum required > version. -- wbr Alexandre Kandalintsev -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
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 "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
