On Fri, 2007-07-06 at 01:21 -0500, Carl Karsten wrote:
> Malcolm Tredinnick wrote:
[...]
> >
> > Some of the MySQL ones are expected, as has been mentioned in threads
> > here recently. Others -- all the encoding-related ones -- look like you
> > might need to set TEST_DATABASE_CHARSET ('utf8' is
Malcolm Tredinnick wrote:
> On Thu, 2007-07-05 at 12:50 -0500, Carl Karsten wrote:
>> I'm slowly getting this a bit more readable, but I won't post duplicates.
>
> Are you asking for help diagnosing these or trying to report a bug?
> You've just posted a bunch of output here without any surroundi
On 7/6/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> The failures shown up by the SQLite are fixed in 5621.
>
> Russell is not allowed to go sky-diving for a week as punishment for
> making that mistake.
Oh. balls.
One of these days I'll remember that there ain't no such thing as a t
On Thu, 2007-07-05 at 12:50 -0500, Carl Karsten wrote:
> I'm slowly getting this a bit more readable, but I won't post duplicates.
Are you asking for help diagnosing these or trying to report a bug?
You've just posted a bunch of output here without any surrounding text,
so it's a bit hard to work
imo, the official documentation should not document bugs, and should
also not provide non-working examples. therefore either the bug should
be fixed immediately, or the example should be removed immediately (to
be re-instated when the bug is fixed). it is true that many bugs
remain in trunk for a
Hello Django Developers,
After the Oracle branch got merged into trunk, the django check
constraints patch code had broken. So I had to fix it (just a one line
change).
Also this week I decided to test the work with databases like SQLite
and Oracle. It worked perfectly with SQLite but there is a s
Thanks!
Ok, I see that the problem is more complicated than I thought, so I'll
leave it that way.
I just want to add that if you decide that you don't like the current
behaviour, you can always use FutureWarning, to first warn if a value
was set and is about to be discarded, and then change the
On 7/5/07, Honza Král <[EMAIL PROTECTED]> wrote:
> We haven't tested it for performance (we are building a high-volume
> site) yet and we still haven't figured out how to deal with multiple
> web servers connecting to one cache (our working version includes
> propagating the post_save signal via s
Sorry, new link: http://dpaste.com/hold/13668/
On Jul 5, 11:41 am, "Honza Král" <[EMAIL PROTECTED]> wrote:
> On 7/5/07, David Cramer <[EMAIL PROTECTED]> wrote:
>
>
>
> > Ya cache invalidation is something you'll always have a problem with.
> > The clean() method can be used (at the end of a query
On 7/5/07, anna <[EMAIL PROTECTED]> wrote:
> It's complicated to explain, but basically, anything that goes onto
> our systems must be approved and only certain versions of Python are
> approved for use/development (2.4 and possibly earlier ones, but I'm
> not sure). We haven't yet chosen a frame
On 7/5/07, anna <[EMAIL PROTECTED]> wrote:
>
> On Jul 5, 11:19 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> >
> > In the Python world, developing "against" a single specific version of
> > the language tends to be frowned upon; there's quite a lot of code out
> > there which runs compatibly on
It's complicated to explain, but basically, anything that goes onto
our systems must be approved and only certain versions of Python are
approved for use/development (2.4 and possibly earlier ones, but I'm
not sure). We haven't yet chosen a framework to use for development
and it would be easier
I recently made a patch that can be used to get a similar result.
You can find the patch here: http://code.djangoproject.com/ticket/4528
regards,
Johan Bergström
On Jul 4, 7:54 pm, Carl Karsten <[EMAIL PROTECTED]> wrote:
> I have the begging of something that may eventually get submitted, and lo
On 7/5/07, David Cramer <[EMAIL PROTECTED]> wrote:
>
> Ya cache invalidation is something you'll always have a problem with.
> The clean() method can be used (at the end of a queryset, or on the
> Manager itself) to force the invalidation.
We have been working on this issue recently and came up wi
On 7/5/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> Oooh, this is something I've wanted to do for ages...See
> http://code.djangoproject.com/ticket/5 , which was marked as wontfix
> by Jacob (but I'd still like to see this feature).
I'd also be interested to get input from the SoC student who
On Jul 5, 2007, at 10:19 AM, James Bennett wrote:
> Django is compatible with any version of Python greater than 2.3, as
> noted in the Django installation documentation:
>
> http://www.djangoproject.com/documentation/install/
You mean >=, right? :-)
Don
--~--~-~--~~~
On 7/5/07, David Cramer <[EMAIL PROTECTED]> wrote:
> So I had a cool little idea -- to build a CacheManager, which let our
> team collaborate with caching controls and not duplicating data in the
> cache.
>
> So, here's a rough draft that i hammered out in 15 minutes.
>
> http://www.davidcramer.ne
On 7/5/07, anna <[EMAIL PROTECTED]> wrote:
> Just in case anyone knows, is it the same with the other frameworks
> for Python, like Pylons, Turbogears, etc? I'm thinking yes, based on
> your answers here, but just wondering.
In the Python world, developing "against" a single specific version of
I think you may want to /join #python on irc or somehting, because there really
wasn't an answer given, so not sure what answer you think you got.
Python code is not developed in Python. that can be debated, but for the
purposed of this thread, I think it fits.
That is like asking "what kind
On 7/5/07, anna <[EMAIL PROTECTED]> wrote:
>
> On Jul 5, 10:42 am, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
> >
> > I think you're asking an unanswerable question; Django is developed
> > *against* a particular minimum Python version's specification.
> > Someone could, in theory, hack on Django with
Why is that unfortunate?
It's just that Django is compatible with Python versions 2.3, 2.4 and
2.5. I would have thought that was a good thing. It just means that you
can install any of the above versions of Python with the latest version
of Django and it will all work.
You would need to look
On 7/5/07, anna <[EMAIL PROTECTED]> wrote:
>
> Ok, thanks. That's the answer I was afraid of, unfortunately.
>
> Just in case anyone knows, is it the same with the other frameworks
> for Python, like Pylons, Turbogears, etc?
Yes.
Why is the answer unfortunate? The answer is not bad-- the ques
I'm slowly getting this a bit more readable, but I won't post duplicates.
Carl K
Updated to revision 5620.
./runtests.py --settings settings_sqlite 2>&1|tee --append runtests.log
./runtests.py --settings settings_mysql 2>&1|tee --append runtests.log
sqlite (failures=2)
mysql (failures=5)
Ok, thanks. That's the answer I was afraid of, unfortunately.
Just in case anyone knows, is it the same with the other frameworks
for Python, like Pylons, Turbogears, etc? I'm thinking yes, based on
your answers here, but just wondering.
Thanks again,
Anna
On Jul 5, 10:42 am, "Tom Tobin" <[EM
On 7/5/07, anna <[EMAIL PROTECTED]> wrote:
> On Jul 5, 10:19 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> > On 7/5/07, anna <[EMAIL PROTECTED]> wrote:
> >
> > > Can anyone tell me what version of Python the latest version of Django
> > > (and previous versions if available) is written/develope
On 7/5/07, anna <[EMAIL PROTECTED]> wrote:
> Yes, I understand that. But does that mean that it's developed in
> 2.3, 2.4 and 2.5 or just one of those? I know this is a weird
> question, but I'm doing research for work and need to know this info.
> The fact that it's just compatible with version
Yes, I understand that. But does that mean that it's developed in
2.3, 2.4 and 2.5 or just one of those? I know this is a weird
question, but I'm doing research for work and need to know this info.
The fact that it's just compatible with versions greater than 2.3 is
not enough - I need to know t
On 7/5/07, anna <[EMAIL PROTECTED]> wrote:
> Can anyone tell me what version of Python the latest version of Django
> (and previous versions if available) is written/developed in? Or can
> you tell me where I can find that info?
Django is compatible with any version of Python greater than 2.3, a
Hi all,
Can anyone tell me what version of Python the latest version of Django
(and previous versions if available) is written/developed in? Or can
you tell me where I can find that info?
Thanks,
Anna
--~--~-~--~~~---~--~~
You received this message because you
Russell Keith-Magee wrote:
> On 7/5/07, Nis Jørgensen <[EMAIL PROTECTED]> wrote:
>> Carl Karsten skrev:
>>> I have the begging of something that may eventually get submitted, and
>>> looking
>>> for guidance as I build it.
>>>
>>> In the spirit of DRY, I have a nifty script that helps create the
Hi list,
This week I continued to work on the "startapp" command of
django.core.management and changed its default behaviour to create a
standalone application (with skeleton files) when you run: "django-
admin.py startapp myapp". Current skeleton files are: release.py,
setup.py, MANIFEST.in, doc
On 5 Jul., 09:41, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-07-05 at 00:39 -0700, jedie wrote:
> > The documentation philosophy is relevant for me: The documentation
> > should really never show non-working examples.
>
> Unsurprisingly,weare in100%agreement. So if the documentat
On 7/5/07, Nis Jørgensen <[EMAIL PROTECTED]> wrote:
>
> Carl Karsten skrev:
> > I have the begging of something that may eventually get submitted, and
> > looking
> > for guidance as I build it.
> >
> > In the spirit of DRY, I have a nifty script that helps create the db
> > defined in
> > setti
On 7/5/07, Noam <[EMAIL PROTECTED]> wrote:
>
> The conclusion is that auto_now_add should set the date only if it is
> None. Or, another solution: it should set the date upon instance
> creation, not upon saving.
FYI - this is a known problem, with scope and ramifications much
larger than the pro
On Thu, 2007-07-05 at 11:52 +0200, Nicola Larosa wrote:
> jedie wrote:
> > Sorry, you have misunderstood this. Thus I have not meant this. ;)
> >
> > Fixing the ticket #1015 is not important to me.
>
> Insisting on telling people what to do, and not really doing anything
> yourself, is obnoxious
jedie wrote:
> Sorry, you have misunderstood this. Thus I have not meant this. ;)
>
> Fixing the ticket #1015 is not important to me.
Insisting on telling people what to do, and not really doing anything
yourself, is obnoxious.
Please make a patch first, and then quibble, preferably in the tick
Carl Karsten skrev:
> I have the begging of something that may eventually get submitted, and
> looking
> for guidance as I build it.
>
> In the spirit of DRY, I have a nifty script that helps create the db defined
> in
> settings.py
>
[snip]
> I am thinking it would be nice if it was hung o
Malcolm Tredinnick skrev:
> On Thu, 2007-07-05 at 00:39 -0700, jedie wrote:
>
>> The documentation philosophy is relevant for me: The documentation
>> should really never show non-working examples.
>>
>
> Unsurprisingly, we are in 100% agreement. So if the documentation and
> the code are
On Thu, 2007-07-05 at 10:52 +0300, Noam Raphael wrote:
> On 7/5/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> > It's a backwards-incompatible change, so we'd need a strong reason to
> > change it.
> [...]
> > This line of reasoning is unfortunately not particularly strong. The
> > problem
On 7/5/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> It's a backwards-incompatible change, so we'd need a strong reason to
> change it.
[...]
> This line of reasoning is unfortunately not particularly strong. The
> problem is that one group of people might find the current behaviour of
> so
On Thu, 2007-07-05 at 00:39 -0700, jedie wrote:
> On 4 Jul., 09:51, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > On Wed, 2007-07-04 at 00:30 -0700, jedie wrote:
> > > "shortly"... But my "change docu" ticket is opened 2 weeks ago:
> > >http://code.djangoproject.com/ticket/4649
> >
> > > The r
On 4 Jul., 09:51, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> On Wed, 2007-07-04 at 00:30 -0700, jedie wrote:
> > "shortly"... But my "change docu" ticket is opened 2 weeks ago:
> >http://code.djangoproject.com/ticket/4649
>
> > The real bug is 2 years old and last modified 2 weeks ago, too:
>
On Thu, 2007-07-05 at 07:30 +, Noam wrote:
> Hello,
>
> The question is, as I see it, what bad thing would happen if
> auto_now_add would set the date only if it's None.
It's a backwards-incompatible change, so we'd need a strong reason to
change it.
[...]
> I think that it would save othe
Hello,
The question is, as I see it, what bad thing would happen if
auto_now_add would set the date only if it's None. I think that
nothing bad would happen - why should someone manually set the date
and expect it to be overwritten? If you agree, I suggest that it will
be changed, because I think
Ya cache invalidation is something you'll always have a problem with.
The clean() method can be used (at the end of a queryset, or on the
Manager itself) to force the invalidation.
As for _get_sql_clause I guess I could make it just pull from filters/
extra args to build the key -- not as clean b
45 matches
Mail list logo
