>
>
> you can see the tests at http://ci.djangoproject.com/ -- currently Oracle
> is untested cause it's a major pita to setup on ubuntu.
>
Thanks for the info.
If anyone is interested, I get 11 failures and 5 errors on master against
Oracle with ./runtests right now:
===
> Unless it fixes a release-blocking regression, it's not possible for
> this to get into either of those release branches.
That's what I thought; just checking.
> Also, generally
> we've been a bit wary of doing any kind of DB pooling at this level in
> the stack...
>
Maybe this patch
Hi, I saw a very old thread talking about setting up a buildbot for Django.
Did this ever go anywhere? Trying to run the tests against Oracle, I'm
finding some that fail against my branch and master. For instance:
ERROR: test_gfk_to_model_with_empty_pk
(regressiontests.generic_relations_regress
forgot to post the
branch: https://github.com/skyl/django/compare/7732-oracle-sessionpool
On Saturday, February 16, 2013 11:17:03 PM UTC-8, Skylar Saveland wrote:
>
> I have a branch on github if anyone is interested in taking a look. I will
> gladly modify and rebase if it's
I have a branch on github if anyone is interested in taking a look. I will
gladly modify and rebase if it's close to being acceptable (it could be
badly flawed, I'm not sure).
I would be interested in getting this (or something like it) into 1.4.X and
1.5.X. Might this be possible?
-Skylar
/17899
>
> Best,
>
> Mark
>
> On Wednesday, December 19, 2012 4:23:24 PM UTC-5, Skylar Saveland wrote:
>>
>> I checked out 1.5 branch today and found a change that I can't find the
>> debate/announcement for: e-mail to email in
>>
>> django/
I checked out 1.5 branch today and found a change that I can't find the
debate/announcement for: e-mail to email in
django/core/validators.py:validate_email = EmailValidator(email_re,
_('Enter a valid email address.'), 'invalid')
This change has me with
# in 1.4.x it is:
#error
Hi,
I posted this in the django-users group but I think it may merit posting
here, as well. I have a test case which I think should pass.
https://github.com/skyl/django/commit/556df1c46146c2fc9c4022d838fa23f652f0ea8d
Is this a bug? If so, is it a bug that is not in the tracker?
Thanks,
Skylar
Ask on django-users. This list is for the discussion of developing django
itself.
sent from my baz foone
-Original Message-
From: Radhikavk
Date: Wed, 21 Apr 2010 22:55:03
To:
Subject: How to set the sucess message after inserting values to db in
django admin site
How to set the su
+1 I would love to join in with some liberal, even wild-eyed experimentation on
github. I have all sorts of cock-eyed ideas that I would like to play with.
I don't like patches; I don't like svn; I'm not a fan of trac. I do however
enjoy the fact that Django trunk leans toward being boring and
Ask user questions elsewhere. This list is for discussing the actual
development of the django framework. You will need to install the mysqldb
python adapter, mysqldb.
sent from my baz foone
-Original Message-
From: rokson
Date: Thu, 28 Jan 2010 06:48:53
To: Django developers
Subject
> Sorry for the problems, folks.
Hey, no worries, thanks for the good work. Seems like a very usable
solution.
--
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 unsu
> ModelForm has a save() method that saves the model. It is reasonable
> to assume that if the form is valid, the save() method call should
> succeed, that's why the entire model is validated.
mf.is_valid() I have understood as validation strictly on the included
fields in the form. I abuse this
13 matches
Mail list logo
