On Mon, 2008-08-25 at 17:41 -0700, Jonathan Nelson wrote:
> Any thoughts on when a beta is going to be released?
Thejaswi's code was reviewed and given a final polish by Jacob over the
last couple of weeks and it was committed to trunk a few hours ago. It
will be in the next release or you can u
django-newcomments is now in trunk.
On Aug 25, 8:41 pm, Jonathan Nelson <[EMAIL PROTECTED]> wrote:
> Any thoughts on when a beta is going to be released?
>
> On Aug 10, 8:50 pm, Thejaswi Puthraya <[EMAIL PROTECTED]>
> wrote:
>
> > Hello,
> > It's been more than three months since I started workin
Any thoughts on when a beta is going to be released?
On Aug 10, 8:50 pm, Thejaswi Puthraya <[EMAIL PROTECTED]>
wrote:
> Hello,
> It's been more than three months since I started working on django-
> newcomments. Ideally, I wished to complete most of my work by July but
> for a relocation and
I tried to contact the TWID gusy through their website, but I haven't
heard back from them. Anyone know if they're still planning a get
together?
On Aug 21, 2:01 am, "Mike Scott" <[EMAIL PROTECTED]> wrote:
> err, link doesn't seem to work with www for me, so try:
>
> http://thisweekindjango.com
On Mon, 2008-08-25 at 19:57 -0400, Michael Hrivnak wrote:
> That is neither a direct nor indirect replacement for model-level validation.
>
> Many applications receive input from sources other than forms. Validation at
> the form and model level are both valuable, but for different reasons.
On Mon, Aug 25, 2008 at 7:57 PM, Michael Hrivnak <[EMAIL PROTECTED]>wrote:
> That is neither a direct nor indirect replacement for model-level
> validation.
> Many applications receive input from sources other than forms. Validation
> at
> the form and model level are both valuable, but for diffe
That is neither a direct nor indirect replacement for model-level validation.
Many applications receive input from sources other than forms. Validation at
the form and model level are both valuable, but for different reasons.
Michael
On Monday 25 August 2008 11:54:31 James Bennett wrote:
> O
I've written a patch, and I could open a bug with post-1.0 milestone,
if that's OK? It's probably a good idea to have a general bug for
initialising HttpResponse objects with iterators.
On Aug 25, 9:33 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Mon, 2008-08-25 at 12:26 -0700, zvoase w
On Mon, 2008-08-25 at 12:26 -0700, zvoase wrote:
> Devels,
> I've noticed in the docs that HttpResponse objects, if initialised
> with an iterator, cannot be used as file-like objects. This could be
> fixed quite easily.
There are lots of problems -- some subtle and some obvious -- when
initia
Devels,
I've noticed in the docs that HttpResponse objects, if initialised
with an iterator, cannot be used as file-like objects. This could be
fixed quite easily. At the moment, if the response was not initialised
with a string, then an error is raised when you try to write to it.
Instead, all
On Mon, 2008-08-25 at 10:29 -0700, Alex G wrote:
> I don't know if this belongs on the dev board, but since it relates to
> how the framework acts, I thought I'd give it a shot. Basically, I am
> curious as to the function of escape vs. conditional_escape, and the
> decision to use the former in
I don't know if this belongs on the dev board, but since it relates to
how the framework acts, I thought I'd give it a shot. Basically, I am
curious as to the function of escape vs. conditional_escape, and the
decision to use the former in the forms.as_x functions...
As far as I can tell, escape
On Aug 25, 10:51 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> I just noticed that the MySQL backend also fails on this get_or_create
> test. It is returning an OperationalError instead of an IntegrityError.
> Looks like MySQL returns errno 1364 (ER_NO_DEFAULT_FOR_FIELD) in this case
> but this
On Sat, 2008-08-23 at 08:07 -0700, Matt Boersma wrote:
[...]
> However, I grep'ed the Django source and found two cases where we
> catch IntegrityError specifically. cx_Oracle probably misbehaves
> there currently, but I'm not sure how common these code paths are and
> what errors could result.
On Mon, Aug 25, 2008 at 12:12 PM, Malcolm Tredinnick <
[EMAIL PROTECTED]> wrote:
> On Mon, 2008-08-25 at 08:47 -0700, Matt Boersma wrote:
> > I can wrap the execute() and executemany() calls in oracle\base.py in
> > a try/except that re-raises this specific error as an IntegrityError:
> >
> >
Hey Matt,
On Mon, 2008-08-25 at 08:47 -0700, Matt Boersma wrote:
> Hi Malcolm,
>
> I can wrap the execute() and executemany() calls in oracle\base.py in
> a try/except that re-raises this specific error as an IntegrityError:
>
> try:
> return Database.Cursor.execute(self, qu
On Mon, Aug 25, 2008 at 10:12 AM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
> So there isn't a direct replacement for validator lists in 1.0.
(other than just setting up the form used for your model in the admin
to have the validation you want, which isn't terribly hard and is how
this sort o
Hi Malcolm,
I can wrap the execute() and executemany() calls in oracle\base.py in
a try/except that re-raises this specific error as an IntegrityError:
try:
return Database.Cursor.execute(self, query,
self._param_generator(params))
except DatabaseError, e:
On Mon, 2008-08-25 at 05:08 -0700, Dennis Schmidt wrote:
> Hi there,
>
> if this will be deactivated in 1.0, how do I have to replace this? I
> couldn't find an easy way like this in the docs yet.
Validators are really only used by the admin in 0.96 (there was no
model-aware validation there).
Hi,
validator_list in model fields (and maybe in form fields too) isn't
working at the moment.
Could we remove it from the docs?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
Hi there,
if this will be deactivated in 1.0, how do I have to replace this? I
couldn't find an easy way like this in the docs yet.
Regards,
Dennis
On 23 Aug., 18:43, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Sat, 2008-08-23 at 16:02 +0200, Alex Rades wrote:
> > Hi,
> > validator_list
On Sun, Aug 24, 2008 at 2:26 AM, James Bennett <[EMAIL PROTECTED]>wrote:
>
> I stand by what I said in the dev channel yesterday: this is one
> instance of a more general issue (there are lots of places where --
> because we need to import or check something -- we can end up
> "swallowing" excepti
-- Forwarded message --
From: Leo Soto M. <[EMAIL PROTECTED]>
Date: Sun, Aug 24, 2008 at 2:53 PM
Subject: GSoC Final Report: Django on Jython
To: JythonDevelopers <[EMAIL PROTECTED]>
Looks like many people already know about my SoC results. But I wanted
to "officially" finish the
23 matches
Mail list logo
