I just spent a couple of evenings tracing a crasher problem that turned
out to be caused by my data. I had some rows with date stamps with a
value of 0 (legacy data). In typecast_timestamp(), this generates a
ValueError because you can't create a datetime object with a year of
less than 1.
This w
It's an interesting idea . . . I know why perforce works this way, but
I'm curious what problem this addresses. Most of the stuff that lives
in the P4CONFIG file is located in /settings.py, as far as I
can tell. And I'm not clear how this would solve the problem of Python
knowing where to look for
IP discussions are worth having, if often painful.I'm far from an expert (or a lawyer), but as a director of the PSF, I unfortunately have a lot of conversations about this stuff.I worry a bit about the current system "scaling" in the long term, as today's core devs may not stick around for 10 year
On Nov 17, 2005, at 7:05 PM, Ian Holsman wrote:
I thought this should be off-line.
Thanks for being sensitive, but there's no reason to and I think
other might be interested so I'm replying back to the list.
but have you guys thought about django's IP?
I see you have trademarked the name,
hugo wrote:
> Sure, people won't be able to use all aspects of
> Django when switching toolkits - but that's the same with ORM and
> template system, you just can't use all aspects of Django when
> switching them to SQLObject or Cheetah.
>
Exactly ;-)
> > I think we should be as toolkit-agnostic as we are
> > templatesystem-agnostic and ORM-agnostic. We deliver one with Django,
> > and all Django code builds on the delivered ones. But we don't enforce
> > those on users, if they want to use something else.
>
> +1 - well put
+1 too.
--
Pedro
Inline.
"Antonio Cavedoni" <[EMAIL PROTECTED]> wrote
in message news:[EMAIL PROTECTED]
>
>along with it. We're in 2005, and we *know* that some people turn JS off
>on purpose, use browsers where JS support sucks, or are disabled
I specifically track js settings of all people who come to my si
Am 17.11.2005 um 23:29 schrieb Antonio Cavedoni:
On 17 Nov 2005, at 11:51, Christopher Lenz wrote:
While there are definitely many types of validations that can't be
performed on the client side, calling back to the server just to
check whether e.g. a text-input is empty is overkill IMO. The
Hello everyone,
first post on the list, I’ll be introducing myself at the bottom of
this message.
On 17 Nov 2005, at 11:51, Christopher Lenz wrote:
While there are definitely many types of validations that can't be
performed on the client side, calling back to the server just to
check wh
I think we should be as toolkit-agnostic as we are
templatesystem-agnostic and ORM-agnostic. We deliver one with Django,and all Django code builds on the delivered ones. But we don't enforcethose on users, if they want to use something else.
+1 - well put
On 11/17/05, Bill de hÓra <[EMAIL PROTECTED]> wrote:
Turn it around. Which of the _javascript_ stacks is working now, or iswilling to work, to make it kick ass with Django?I won't speak for him, but I was talking last night to Alex Russell, of Dojo, and he said that he'd tried to talk to the Django
Inline.
"Christopher Lenz" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> I'd prefer a hybrid approach, where simple javascript validation checks
> are generated, and the others are performed via AJAX callbacks.
+1.
Well-known type validation and simple checks can be (and sh
David Ascher wrote:
>
>
>
> Goofy idea: use the Python logic to generate JS code to do clientside
> validation based on the model-specified constraints. Detailed specification
> and implementation are left as an exercise to the reader. ;-)
>
Scarily:
http://codespeak.net/svn/pypy/dist/pypy/t
lymxz wrote:
> Hi all,
>
> I want to enable recursive edit_inline feature by extending new-admin
> branch, e.g. to add company/office/user in one page. Unfortunately,
> only one level editing inline is supported based on dotted expression
> in current new-admin branch, things like 'office.1.name
Robert Wittams wrote:
> Wilson wrote:
>
>>no matter which framework gets bundled (or if anything gets bundled
>>at all)
>
>
> This is the sticking point. I just have no idea how we add rich
> functionality to the bundled apps without either
>
> a) Picking a toolkit to bundle
> b) Making some h
Am 17.11.2005 um 10:07 schrieb Simon Willison:
On 17 Nov 2005, at 05:48, David Ascher wrote:
Goofy idea: use the Python logic to generate JS code to do
clientside validation based on the model-specified constraints.
Detailed specification and implementation are left as an exercise
to the
Thanks Eugene.
I didn't end up using it.
I have implemented some *basic* JSON outputer's and using ajax
(mochikit) to render them.
the code makes use of json.py and is here
http://svn.zilbo.com/svn/django/snippets/json/
I *doesn't* do datetimes. a demo of the code being used on the 'polls'
app
On 17 Nov 2005, at 05:48, David Ascher wrote:
Goofy idea: use the Python logic to generate JS code to do
clientside validation based on the model-specified constraints.
Detailed specification and implementation are left as an exercise
to the reader. ;-)
Here's a concept for form validat
Hi all,
I want to enable recursive edit_inline feature by extending new-admin
branch, e.g. to add company/office/user in one page. Unfortunately,
only one level editing inline is supported based on dotted expression
in current new-admin branch, things like 'office.1.name',
'office.2.name'. So m
19 matches
Mail list logo
