Re: End-user defined fields, how would you approach it?

[Simon Charette]

I've been working on a similar project which takes the django-dynamo 
project a bit further.

It's undocumented ATM but you can find the code at: 
https://github.com/charettes/django-mutant

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/x6uWMd1KF3QJ.
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.

Generic edit generic views don't create `fail_silently` messages anymore.

[Simon Charette]

Now deprecated generic create_update function based views 
(create_object,
 
update_object,
 
delete_object)
 
use to create silently failing success messages when the submitted form was 
valid. 

Was it a design decision to omit this feature for class based equivalents?

If it was deliberately omitted then, since function based views are 
deprecated, the message framework documentation for the `fail_silently` 
kwarg should be updated to remove the part where it makes reference to 
generic views using it 
internally
.

Here's wip 
patchto
 backport this feature for class based views that I can attach to a 
ticket if this get acknowledged as a missing feature. I can also submit a 
doc revision in the other case.

Simon


-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/E-yNGQ2D1zIJ.
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.

django.forms.fields.Field.localize to default to settings.USE_L10N

[Simon Charette]

Hi, I encountered a problem with DecimalField and DECIMAL_SEPARATOR in the 
admin which lead me
to a ticket [1] which was marked as worksforme.

Well it wasn't quite workingforme so I tried to come up with a testcase 
since the ticket has none.

I realised that the actual implementation of DecimalField was working 
perfecly when it was initialized
with the "localize=True" kwarg. Which lead me to a larger issue concerning 
admin not considering
settings.USE_L10N: ModelAdmin.formfield_for_dbfield should pass the 
localize=True kwarg if
settings.USE_L10N=True. IMHO it's an expected behavior.

I'm also wondering if the issue shouldn't be tackled at the 
forms.fields.Field API level instead.
What about defaulting Field.__init__ localize kwarg to settings.USE_L10N?

Simon

[1] http://code.djangoproject.com/ticket/14101

-- 
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: django.forms.fields.Field.localize to default to settings.USE_L10N

[Simon Charette]

Thank you very much for your feedback, I was wondering
what were the edge cases that motivated such a decision.

Do you believe it makes sense to have such a switch at
the Form level, say a localize keyword which it's fields
would default to? The same could apply to ModelAdmin
localize_forms. If so i'll file a feature request whith a patch
and tests. I might need some help on doc however.

Simon

-- 
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: pb with search on website

[Simon Charette]

This addon[1] has not been updated since the doc were and doesn't work 
anymore.

You can try this updated version[2] I use which works fine.

[1] https://addons.mozilla.org/en-US/firefox/addon/django-docs-search/
[2] https://gist.github.com/813029

-- 
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: Decision for ticket #6362 - Remove blank spaces with strip when validating the data

[Simon Charette]

How is that supposed to interact with the `cleaning` mechanism of the field?

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/BNMXjILUK7gJ.
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: DJango doesn't work with Oracle 11g on Windows 8

[Simon Charette]

http://lmgtfy.com/?q=vcvarsall.bat

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/v6EuZV0jI6AJ.
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: API for introspecting models

[Simon Charette]

It might be worth it to look at this existing effort to document _meta: 
http://readthedocs.org/projects/django-model-_meta-reference/.

Simon

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/FxTT4AIHOG8J.
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: First time contribution, tests fails.

[Simon Charette]

Hi Yasar!

Are you sure you're at the latest trunk revision? (16911)

I'm not getting any failures with this revision and the test_sqlite 
settings?

http://dpaste.com/623028/

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/BFgwixc7umUJ.
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.