newforms: Need ability to pass a RequestContext to FormPreview

[Vadim Macagon]

Hi,

I'm trying to use FormPreview in the formtools module, however it only 
passes a regular Context to templates, whereas my templates rely on a 
RequestContext. I've made some changes to accommodate my templates, more 
info and a diff can be found here:


http://code.djangoproject.com/ticket/3204


Cheers,

-+ enlight +-


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: newforms: Need ability to pass a RequestContext to FormPreview

[Vadim Macagon]

Adrian Holovaty wrote:


In [4259], I changed FormPreview to use RequestContext by default.
Thanks for the report!



That will suit me just fine :)


Thanks,

-+ enlight +-


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: newforms: Need ability to pass a RequestContext to FormPreview

[Vadim Macagon]

Adrian Holovaty wrote:

In [4259], I changed FormPreview to use RequestContext by default.
Thanks for the report!



Dang, just noticed you forgot to add this to preview.py:

from django.template.context import RequestContext

I'd make a patch but it'll probably take you longer to apply it than 
copy/paste this line in :)



-+ enlight +-

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Subversion change notifications

[Vadim Macagon]

Hi,

Sourceforge.net allows developers to subscribe to a Subversion/CVS 
change notification list for any project. It makes it easier to stay up 
to date when working with an ever evolving code base. Is there something 
similar for the Django SVN? I couldn't find any mention of it anywhere.



Cheers,

-+ enlight +-

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Subversion change notifications

[Vadim Macagon]

Thanks :)

The Django-updates group is exactly what I was looking for. This link 
should be more prominently displayed, perhaps here:


http://www.djangoproject.com/documentation/contributing/

and here:

http://www.djangoproject.com/documentation/

I just did a Google search to find if it's mentioned anywhere on 
djangoproject.com and the only page I found was this:


http://www.djangoproject.com/community2/

Except that I couldn't find a way to get to that page by following any 
links on djangoproject.com. Perhaps the poor thing got lost?



-+ enlight +-

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Encouraging contributed documentation

[Vadim Macagon]

+1

I'd also like to see a script that generates a CHM (Compiled HTML Help) 
from the official Django ReST docs. The CHM could then be included as 
part of the installer-based release for Windows users. One of these days 
I'll probably get fed up waiting for the pages on djangoproject.com to 
load and write the damn script myself, unless someone beats me to it :)


-+ enlight +-

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

newforms: accessing help_text in a template

[Vadim Macagon]

Hi,

Currently to access help_text for a field in a template I have to do this:

{{ form..field.help_text }}

would be nicer if I could just do this:

{{ form..help_text }}

A two line change to BoundField will do the trick, I can submit a patch 
if desired.


-+ enlight +-

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

IntegrityError patch

[Vadim Macagon]

Just wanted to point out that I submitted a small patch to make 
IntegrityError available directly from django.db.



I've tested it on the postgresql and postgresql_psycopg2 backends, and 
it'd be nice if people could test it on the other backends.


Thanks,

-+ enlight +-

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: changeset 4394 broke QuerySet.iterator() interface

[Vadim Macagon]

Gary Wilson wrote:
> google ate "[4394]" off of my subject
> 

Err, no it didn't.

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: IntegrityError patch

[Vadim Macagon]

Vadim Macagon wrote:
> Just wanted to point out that I submitted a small patch to make 
> IntegrityError available directly from django.db.
> 
> <http://code.djangoproject.com/ticket/3450>
> 
> I've tested it on the postgresql and postgresql_psycopg2 backends, and 
> it'd be nice if people could test it on the other backends.

It's now been sitting at the "Accepted" stage for 4 weeks, what do I 
need to do to move it to the next stage?


-+ enlight +-


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---