On Apr 12, 2:00 pm, Karen Tracey wrote:
> Adding re.escape in that function does break some tests, from a quick look
> it seems mostly ones that are raising multiple errors but only one has been
> listed by the caller of that utility function. It isn't clear to me from the
>
On Mon, Apr 11, 2011 at 10:17 PM, Julien Phalip wrote:
> I'm not sure how to properly fix this or where the core issue is. Am I
> missing something or is it worth opening a ticket?
>
I think there's definitely a problem with that assertFieldOutput utility
function. That 2nd
Hi,
I've found two similar (and potentially linked) weird problems in the
test framework while trying to understand why the perfectly looking
tests in #14608 were failing. Before I open some tickets I'd like to
hear if anybody has any clue about what's going on or if I'm missing
anything.
1)
On Mon, Apr 11, 2011 at 12:27 PM, Amit Reks wrote:
> We have an opening for a Python Developer in San Jose, CA.
Amit, this is the second time you've posted off-topic unwelcome job
ads to this list. Don't do it again or I'll be forced to ban you.
Jacob
--
You received this
Amit,
Please make job postings to the django-users mailing list. The
django-developers list is for discussion related to the development of
Django itself.
Thank you.
Tobias
On Mon, Apr 11, 2011 at 3:27 PM, Amit Reks wrote:
> Hi,
>
>
>
> Greetings!!!
>
>
>
> We have an
Hi,
Greetings!!!
We have an opening for a *Python Developer* in San Jose, CA.
We would highly appreciate it if you could recommend someone for it, in case
you are not interested...
Please find the job description below.
*Job Title: Python Developer*
*Job Location: San Jose, CA*
On Sat, Apr 9, 2011 at 4:42 PM, Graham Dumpleton
wrote:
>
> On Saturday, April 9, 2011 5:35:14 PM UTC+10, Russell Keith-Magee wrote:
>>
>> On Sat, Apr 9, 2011 at 2:15 PM, Graham Dumpleton
>> wrote:
> Anyway, as you can see the above is a pain
The main purpose of the height_field and width_field attributes is to
give a performance boost in some situations,
these fields acting as a cache on the dimensions of the image.
I recently have switched-on those attributes for a newspaper
publishing project where we manipulate some huge .tiff
I'm just going through some code in an application and adjusting it to
work with Django 1.3 and I thought I'd have to fix a portion of code
to account for the change in transactions meaning that a
cursor.execute call would leave a transaction in a dirty state (even
tho' it didn't change anything).