On Thu, Sep 9, 2010 at 11:26 AM, Simon Litchfield wrote:
> Hi all
>
> Default behaviour of sending an email on 500 error is great.
>
> Problem is on high traffic sites, and you might just be making a quick
> update- literally within seconds you can bring your mail server down-
> crash your mail cl
On 08/09/10 09:22, Patryk Zawadzki wrote:
>> 1) Use of IP address - a bad idea for the reasons I mentioned in my
>> other message.
>
> A lot of web frameworks I've worked with use the IP to lock the
> session cookie to prevent easy cookie theft.
... just mentioning the existence of django-parano
Hi,
some days ago I uploaded a new patch for this ticket:
http://code.djangoproject.com/ticket/9459
Here is the patch:
http://code.djangoproject.com/attachment/ticket/9459/datetime-microseconds-py25.patch
If the python version is greater-equal than 2.6, it uses %f to parse the
microseconds,
fo
from Eric Florenzano's slide 41:
In models.py:
class Favorite(models.Model):
item = LazyForeignKey(‘fave’)
user = ForeignKey(User)
date = DateTimeField(default=utcnow)
In settings.py:
LAZY_FKS = {‘fave’: ‘pages.models.Page’}
I share the dislike for generic relations
On Thu, Sep 9, 2010 at 4:24 PM, Javier Guerra Giraldez
wrote:
> from Eric Florenzano's slide 41:
> (...)
You might want to take a look at my little sandbox here:
http://room-303.com/blog/2010/04/27/django-abstrakcji-ciag-dalszy/
(Sorry the post is in Polish but the only interesting part is the
Hi Javier,
after GSoC 2010, we have
http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/django/t127230758002
feature at
http://code.djangoproject.com/browser/django/branches/soc2010/app-loading
Not that good syntax, but this solution can help you!
P.S. The more testers we have,
Hi folks --
A bit of context before I dive in: at DjangoCon, Eric Florenzano gave
a "what's broken about Django" talk. I sadly had to miss DjangoCon,
and so I'm anxiously waiting to see the video, but I did see one thing
in the slides I thought I should address right away. Actually, this is
someth
On do, 2010-09-09 at 12:30 -0500, Jacob Kaplan-Moss wrote:
> The goal is to only be private when we absolutely *must*, and if we're
> not sufficiently transparent *please* say something.
Thanks Jacob, for explaining this.
This makes a good amount of sense, and Django is not unique here. I am
in
Thanks Jacob,
I don't understand why we are discussing about it.
It's quite obvious that if there is a core team, there's also a mailing
list.
S
On Thu, Sep 9, 2010 at 19:30, Jacob Kaplan-Moss wrote:
> Hi folks --
>
> A bit of context before I dive in: at DjangoCon, Eric Florenzano gave
> a
hello friends:
I have good news for you. Last week ,I have Order china 7
Products
w e b: www.hoaoeso1.com I have received the product!
It's amazing! The item is original, brand new and has high quality,
but it's muc cheaper. I'm pleased to share this good news with you!
I believe you will find
On Thu, Sep 9, 2010 at 10:24 PM, Javier Guerra Giraldez
wrote:
> from Eric Florenzano's slide 41:
>
> In models.py:
>
> class Favorite(models.Model):
> item = LazyForeignKey(‘fave’)
> user = ForeignKey(User)
> date = DateTimeField(default=utcnow)
>
>
> In settings.py:
>
> LAZY_F
On Thu, Sep 9, 2010 at 1:59 PM, Russell Keith-Magee
wrote:
> On Thu, Sep 9, 2010 at 10:24 PM, Javier Guerra Giraldez
> wrote:
>> from Eric Florenzano's slide 41:
>>
>> In models.py:
>>
>> class Favorite(models.Model):
>> item = LazyForeignKey(‘fave’)
>> user = ForeignKey(User)
>>
On Thu, Sep 9, 2010 at 10:59 PM, Russell Keith-Magee
wrote:
> The LazyForeignKey pattern has been proposed by a number of parties;
> it's an interesting idea that is worth some serious consideration.
> There are some issues with implementation (e.g., exactly how to
> describe the relationship in a
Hi,
this proposal is about extending the storage backend api of Django.
The storage backend has already many helpful methods to get information
about stored files like:
- name
- size
- full path (for some backends).
I think it could be useful to have some more methods to get information
abou
On Thu, Sep 9, 2010 at 3:59 PM, Russell Keith-Magee
wrote:
> What you're proposing here is two things: a LazyForeignKey, and
> configurable applications.
not really, it's only configurable applications. once you have that,
it's easy to make the ForeignKey depend on a parameter.
> Configurable
+1. Explaining existence of private core-list is needless.
But also +1 for other points in Eric's presentation.
Thanks Jacob,
I don't understand why we are discussing about it.
It's quite obvious that if there is a core team, there's also a
mailing list.
S
--
You received this message b
On Thu, Sep 9, 2010 at 4:02 PM, Alex Gaynor wrote:
>>> INSTALLED_APPS = (
>>> 'django.contrib.auth',
>>> 'django.contrib.contenttypes',
>>> 'django.contrib.sessions',
>>> 'django.contrib.sites',
>>> 'django.contrib.admin',
>>> ('debug_toolbar', {
>>>
On Fri, Sep 10, 2010 at 6:42 AM, Javier Guerra Giraldez
wrote:
> On Thu, Sep 9, 2010 at 4:02 PM, Alex Gaynor wrote:
>> So how does this work? Where do args come from?
>
> args (for lack of a better name) is the same dictionary passed as the
> second part of the tuple in the INSTALLED_APPS list.
I disagree. Although it is normal for a project to have private
mailing lists, such as -security, I'm very glad Jacob took the time to
explain the need for its presence in Django. And a big +1 on
scheduling releases in public.
J. Leclanche
On Thu, Sep 9, 2010 at 11:41 PM, Anton Bessonov wrote
On Thu, 2010-09-09 at 12:30 -0500, Jacob Kaplan-Moss wrote:
> 1. Security-related issues. When we receive a security report, we need
> to discuss it in private.
Just as a data point...
I'm a committer on a widely-used open source application, and we discuss
these things on a "packagers" list. As t
I forgot to mention the ticket for the "stat" method:
http://code.djangoproject.com/ticket/10497
Stephan Jäkel wrote:
FYI, there is a ticket in trac which recommends to add a "stat" method
but I think this maybe would be hard to implement on backends like S3.
Cheers,
--
You received this mess
On Sep 10, 8:41 am, Anton Bessonov wrote:
> +1. Explaining existence of private core-list is needless.
I would say that any information on why a structure exists is good.
The Apache Software Foundation would be a good example of where a lot
of effort has been taken to explain how things work.
On Sep 9, 2010, at 7:24 AM, Javier Guerra Giraldez wrote:
> what about giving parameters to the apps? something like:
>
> INSTALLED_APPS = (
> 'django.contrib.auth',
> 'django.contrib.contenttypes',
> 'django.contrib.sessions',
> 'django.contrib.sites',
> 'django.c
On Thu, Sep 9, 2010 at 5:43 AM, Thomas Guettler wrote:
> Here is the patch:
>
> http://code.djangoproject.com/attachment/ticket/9459/datetime-microseconds-py25.patch
>
> If the python version is greater-equal than 2.6, it uses %f to parse the
> microseconds,
> for older versions it parses the las
Hi all,
It looks like we'll be needing a fairly prompt 1.2.3 release. So far
we've got:
One major/critical bug (depending on how many people are using the
deprecated CsrfResponseMiddleware):
http://code.djangoproject.com/ticket/14235
One significant regression:
http://code.djangoproject.com/t
I disagree. Although it is normal for a project to have private
mailing lists, such as -security
You disagree, but it is normal? Decide for you first.
I'm very glad Jacob took the time to
explain the need for its presence in Django.
There is a difference about knowledge of the confidential lis
On Fri, Sep 10, 2010 at 1:17 AM, Anton Bessonov wrote:
>
>> I disagree. Although it is normal for a project to have private
>> mailing lists, such as -security
>
> You disagree, but it is normal? Decide for you first.
I disagree that there was no explanation necessary. As Graham very
elegantly pu
I would say that any information on why a structure exists is good.
There is no difference have developers a confidential list, a chat or
they communicate by phone, right? It has no relation to structure. It is
a natural way for the decision not public problems.
--
You received this mes
I have read that this talk was well received at Djangocon and caused some
great discussions and I would just like to put my hand up and say I've
encountered most of the technical issues Eric's slides talk about. I'm an
edge case in many ways (I am integrating with a legacy system) so I
haven't thou
On Thu, Sep 9, 2010 at 8:59 PM, Luke Plant wrote:
> Hi all,
>
> It looks like we'll be needing a fairly prompt 1.2.3 release. So far
> we've got:
>
> One major/critical bug (depending on how many people are using the
> deprecated CsrfResponseMiddleware):
>
> http://code.djangoproject.com/ticket/1
> Unfortunately we didn't catch this failure in four weeks, the fact
> that the buildbot
> isn't running tests for the 1.2.X branch doeesn't help either.
The buildbot actually is running the 1.2.x tests, it is just
unfortunately named (and apparently re-naming it is a bit of a pain so
it hasn't ha
31 matches
Mail list logo
