On Sun, Sep 20, 2009 at 6:13 PM, Chris Beaven wrote:
> Having some kind of defacto cross-request notification system makes
> sense; it's a very common usage pattern.
> Attaching these kind of messages to a User instance is wrong: there is
> not an enforced one to one correlation between a user an
On Sun, Sep 20, 2009 at 10:24 AM, Russell Keith-Magee <
freakboy3...@gmail.com> wrote:
>
> You also mention that there are a number of other implementations, but
> you haven't really given a compelling survey or analysis of the
> alternatives - you've just blessed one in particular. Why?
>
I start
dows of one browser? Then message could
> appear in different window not the right one where we invoke the
> event. Is it a problem? Is only possibility to get of this issue that
> flash app should add a query parameter into redirected url which would
> identify the right window?
>
> V
On Tue, Sep 22, 2009 at 9:51 PM, Russell Keith-Magee wrote:
> In reality, I get a ping time closer to 300 ms. And that's to a
> high-end data center under ideal conditions - it can be much larger if
> I'm dealing with low end providers.
>
What?? 200 ms is the average quoted by Mr. Sproutcore him
+1 for signed cookies. Your API looks reasonable and I'd agree that
set_cookie(..., signed=True) fits better with the rest of the API as well.
What about some sanity checking to make sure that, if SECRET_KEY is used, it
is, at the very least, a non-empty string?
On Thu, Sep 24, 2009 at 1:18 PM, S
On Thu, Sep 24, 2009 at 5:33 PM, Chris Beaven wrote:
>
> Personally, I don't see much point in specifically reporting on
> incorrectly signed cookies - imo they should just be treated as if
> they never existed. If someone really cared, they can look in
> request.COOKIES to see if the cookie was i
idn't write the test, can be the
difference between a 2 minute fix and a half hour+ debugging session.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--~--~-~--~~~---~--~~
Y
/SessionMessages#TODOOnceaSolutionisChosen)
Cheers,
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On Sat, Oct 10, 2009 at 1:19 PM, Tobias McNulty wrote:
> Things that still need to be discussed/done:
>
> * Coming to consensus on what 3rd party app we actually choose to
> extend/modify to fit into Django
>
> * What to do with the existing user message API (see
> http://c
On Sat, Oct 10, 2009 at 2:05 PM, David Cramer wrote:
> The proposal per your email is more or less how django-notices works.
For comparison I added django-notices to the Available Options:
http://code.djangoproject.com/wiki/SessionMessages#AvailableOptions
--
Tobias McNulty
Caktus Consult
http://code.djangoproject.com/wiki/SessionMessages#Criteria
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
the first release od django
> messaging. I think django isn't now in right mood to add there some
> functionality like adding of query parameters to response object by
> some application. Maybe in future.
AFAIK this will become a non-issue with the advent of HTML5, as each
window/tab wil
In case it's not already on someone's radar, the patch on this ticket
could use a review at some point:
http://code.djangoproject.com/ticket/9310
Thanks -
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktu
Another quick bug fix that should be ready for review/check-in:
http://code.djangoproject.com/ticket/11872
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--~--~-~--~~~---~--~~
You
the extra database or cache hit.
It seems well worth it to me and there are solutions out there that
try to store the messages in a cookie and then fall back to the
session for longer (>4kb) messages.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(
ki page say as much, but I
should probably clarify that django-notify does not actually provide
any default levels/classes/tags yet. Thanks for the feedback.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
ext request, and in most other cases removed on the subsequent
request (e.g., in the case of 2+ chained redirects).
The point is just to keep them around until they're actually
displayed, not indefinitely.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
ticular issue with allowing messages to be iterated in
full and/or by type. We could also just sort the messages and let you
use {% regroup messages by tag %}, but I suppose you want the ability
to pull out a particular type of error and that could get tedious with
{% regroup %}.
Tobias
--
Tob
of keeping things simple, let's assume it will not be included unless
someone brings up a compelling case.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--~--~-~--~~~---~--~~
core devs (and from some of the folks who were involved in
this discussion back when it was happening on the ticket) on the wiki
page[1] and the general direction this project is going.
Tobias
[1] http://code.djangoproject.com/wiki/SessionMessages
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O.
and fewer letters in the actual message (before the line hits 80
chars).
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--~--~-~--~~~---~--~~
You received this message because you are s
a static
logging level (e.g., INFO)
I like #2, provided that the default logging handler in Django is a
NullHandler (I think it is/will be).
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--~--~-~--~~-
ficially deprecated but continues to work unaffected
1.3: user.message_set is still usable, but raises a deprecation
warning when it is used
1.4: user.message_set is removed
Are we comfortable ditching the auth Message model altogether (several
releases from now), or is someone actually using it for a legitim
nctionality.
Unless there is a compelling use case for user-based messages that
really sets it apart from the proposed app (and there may very well
be, I just haven't heard it yet), my vote is to deprecate the Message
model in contrib.auth in a gradual way and remove it altogether
several rel
rather make the conscious switch from one
technology to the other. IMHO I don't think the effort and potential
confusion of making everyone's templates "just work" is worth it.
Chris, I know you have some personal experience trying to get session-
and user-based messages to wo
with user.message_set (and
potentially deprecate the old API) is a key priority and something we
DO need to hammer out more. That said I think we can get it done.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgrou
a skeleton of a plan (not much more than what I sent before)
on the wiki:
http://code.djangoproject.com/wiki/SessionMessages#DeprecationPlan
There are still a few things missing (like what apps actually need to
be updated) but hopefully that'll provide us a place to keep track of
the details
o see
> something like it make it's way into core.
That's an option. It's short and doesn't conflict with anything that
I know of. I added a section to the wiki with potential app names:
http://code.djangoproject.com/wiki/SessionMessages#PotentialAppNames
--
Tobias McNulty
ny wisdom to share about this? I expect it may be
complicated because I can't think of a clean way to get the current
request (and hence the session messages variable) inside the User
model.
Maybe I'm missing something.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box
upgrade path from the old API? Or is there still concern
about naming?
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--~--~-~--~~~---~--~~
You received this message because you are su
API on the wiki:
http://code.djangoproject.com/wiki/SessionMessages
Cheers,
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--~--~-~--~~~---~--~~
You received this message because you are subscrib
hich has
> no variable,and it's so easy for you guys, isn't it?
This would be a lot easier to discuss if you (or someone else) can
show us (a) an implementation of such a tag, and (b) some profiling
numbers that demonstrate significant savings with your method.
Tobias
--
Tobia
>
>
> David Cramer
>
>
>
> On Fri, Oct 16, 2009 at 1:08 PM, Tobias McNulty
> wrote:
>>
>> On Fri, Oct 16, 2009 at 5:10 AM, Luke Plant wrote:
>> > I think this means that either the deprecation cycle would have to
>> > pushed back one (i.e. p
nced to skip the compatibility function and go
straight to raising an error, but that seems like a big jump.
I updated the branch to do basically this, but nothing is set in stone.
Thoughts?
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
ht
ll the ramifications
of (a) would be (and there wouldn't be much point anyway, since
there'd be no way to get a message into the cookie or session storages
without the middleware).
Now that I think about it, this is probably what you meant and just
wanted to make sure the messages context_p
registration to contrib.
Agreed. The "pluggable work flow" that is Django itself works quite
well for me.
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--~--~-~--~~~---~--~~
hoice you have in schema evolution tools
a Good Thing. Integrating something into the core may tie to you to a
specific implementation that doesn't really suite your needs. So
what's the big rush?
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 2
's a de facto place to look for apps
yet, but I bet a winner will emerge in time.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--~--~-~--~~~---~--~~
You received this message be
he domain name, then
include the project folder under that. There's nothing stopping you from
housing more generic apps outside the project namespace.
On a related note, an on-going pet peeve of mine is that manage.py leaves
'.' on the python path. This can be confusing for new us
wers at
be (though I should think anyone is free to make serious, well thought out
proposals in the wiki, whatever they might be). :)
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--~--~-~--~~~--
;s being overlooked. If some developers
> want to create awful UIs who are we to stop them? Other devs trying to
> quickly prototype code or who just don't need prettier layouts hit
> major roadblocks here. Django should easily handle the common cases,
> not try to enforce good web
I'm no designer either but I perhapsit could do with a bit of attention
> from
> > one, I'm not that keen on the red (pink?) and green mix.
> >
> > Also, documentation will be needed so users know what the colours mean
> but
> > I'm not sure where
essages.txt
If your comments wouldn't benefit from discussion, feel free to email them
to my privately to avoid swamping the list.
Thanks,
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
h
On Tue, Nov 3, 2009 at 8:31 AM, Yuri Baburov wrote:
>
> On Tue, Nov 3, 2009 at 9:27 AM, Tobias McNulty
> wrote:
> > I'm not a big fan of the red/green either. They imply that Django code
> is
> > "bad" and user code is "good".
> The opposite
to me as well; I'll make the change.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Gro
he rest of the code base, especially about
> transition issues. However, I didn't want to start in on a big
> teardown unless you thought the code was ready for it. When you're
> ready for a the full latex-glove treatment, let me know. :-)
>
Will do. I have a little cleanu
eady for a the full latex-glove treatment, let me know. :-)
>
Tear it apart :-)
Diff showing latest changes in branch uploaded to ticket:
http://code.djangoproject.com/attachment/ticket/4604/django-contrib-messages-9f54c0f8719c.diff
Cheers,
Tobias
--
Tobias McNulty
Caktus Consulting Group, LL
or most cases; hopefully this is
something that folks using sessions and cookies are prepared to deal with.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--
You received this message because you are subscribed to the Go
cy - just say that the policy will
> be followed and provide a link to the original source.
>
Removed.
Additionally, per your other email, I added some notes to the docs about
behavior of parallel requests from the same client.
Again, the only thing I can think of that still needs to be wor
ar feedback from
others before moving forward, in case there's something we missed. I
updated the wiki to reflect the new proposed API:
http://code.djangoproject.com/wiki/SessionMessages#PotentialAPI
Once the final API changes have been made, I'll put up another patch,
hopefully befo
e sponsors so far, but there's still room for more, so check
out the sponsors section of the wiki and add yourself (or your company) if
you'd like to bring something.
Hope to see you there!
Cheers,
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(
@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>
>
--
Tobias McNulty
Caktus Consulting Group, LLC
t you cannot rely on there being a current authenticated
> User. Docs should include something about it being intended for re-
> usable apps.
>
Good catch. fail_silently sounds good to me. I'll add.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 2
Latest patch, including fail_silently, is up for review:
http://code.djangoproject.com/attachment/ticket/4604/django-contrib-messages-e4da706e1152.diff
Cheers,
Tobias
2009/12/3 Tobias McNulty
> The simplest solution is to catch the exception in the generic views.
>> Another option is
It's also a good thing, I realized last night, because it means one can use
messages from a reusable app without requiring that all projects using the
app enable messages.
Cheers,
Tobias
Sent from a mobile phone, please excuse any typos.
On Dec 3, 2009 6:25 AM, "Russell Keith-Magee"
wrote:
On
the previous implementation. Am I missing
something?
<http://bitbucket.org/tobias.mcnulty/django-contrib-messages/src/tip/django/contrib/messages/api.py#cl-38>
Cheers,
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.co
Is there a page where one can find a quick summary of the proposed API?
I have some concerns about implementing partitioning through the admin, but
I expect there's something I'm missing.
For those who haven't been, following the conversation closely it'd be nice
to have a quick way to come up to
}
}
The admin could automatically take advantage of this setting to
determine what database to use for a given model.
Cheers,
Tobias
On Fri, Dec 4, 2009 at 10:47 AM, Russell Keith-Magee
wrote:
>
> On Fri, Dec 4, 2009 at 11:40 PM, Tobias McNulty
> wrote:
> > Is there a page
e way that also fixes other issues with the current
implementation (namely, the admin).
That said, figuring out the right way to implement it is still up in
the air. I proposed a separate setting; Paul proposed one integrated
with the DATABASES setting. There are likely better ways to do it and
?
> Monkeypatch it? Make patched version for each app? Well, then please
> provide a method which will do this override for all models if called
> from a single place in project, probably, settings.
>
> In large projects, single point of override on per-project basis is
> required,
.Site method be useful in addition to
whatever more global method we come up with for designating what
tables go in what databases, or will it be obsolete (and potentially
deprecated) at that point? I can't see a reason that one would want
to modify the database(s) the admin uses irrespec
easonable (and already supported?) workaround for
those who need to modify the admin to use a different database in specific
cases.
Cheers,
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--
You received this message beca
up as an ..admonition:: , and should probably have an example to show
> the correct technique.
Good call, added, thanks.
Other than the question about renaming storage -> backend I think we
are close to prime time. Let me know what you think.
Cheers,
Tobias
--
Tobias McNulty
Caktus Co
ot;Idiocy: Never underestimate the power of stupid people in large
> groups." (despair.com)
>
> Luke Plant || http://lukeplant.me.uk/
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post
ng to give this a final whirl by converting a project or two.
Cheers,
Tobias
On Sat, Dec 5, 2009 at 2:05 PM, Tobias McNulty wrote:
> It looks like I mis-read the original question about storage vs.
> backend, so thanks for picking this up Luke.
>
> I don't have much to add to your
uld be backwards compatibility issues
to deal with, but that's an issue the project will have to take on in
a much larger way regardless when/if backend standardization becomes
an established goal.
Cheers,
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919
Just wanted to add that the decision need not go either way; one possible
solution would be to leave it up to the implementation and live with both
conventions in the core.
Sent from a mobile phone, please excuse any typos.
On Dec 7, 2009 7:17 AM, "Russell Keith-Magee"
wrote:
Hi all (and especi
as commit granularity in terms of features (even small bug
fixes) is usually a Good Thing.
Cheers,
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--
You received this message because you are subscribed to the Google
On Mon, Dec 7, 2009 at 4:59 PM, Jacob Kaplan-Moss wrote:
> Additionally, a few features are in or close to last-call stage
> (multidb and the smarter if tag).
You can add the messages framework to the list of features that will
be in Real Soon.
Cheers,
Tobias
--
Tobias McNulty
point.
Thoughts?
Tobias
On Mon, Dec 7, 2009 at 7:25 AM, Russell Keith-Magee
wrote:
> On Mon, Dec 7, 2009 at 3:05 AM, Tobias McNulty wrote:
>> On Sat, Dec 5, 2009 at 10:24 PM, Russell Keith-Magee
>> wrote:
>>> However, I'm also willing to admit that personal prefer
deprecation warning now
(since it is using deprecated code, after all)? Alternatively, since
the warning may be a little obscure (the user is not using message_set
directly), we could make LegacyFallback itself raise a deprecation
warning.
That would encourage folks to move to Fallback sooner rat
ian/pony-build-django
Branch and go?
Cheers,
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To po
rac is code.djangoproject.com running? Supposedly
this bug was fixed almost two years ago:
http://trac.edgewall.org/ticket/6199
If 0.11.X, the fix could be as easy as easy_install --upgrade Trac. I
did it last night on our multi-project, many-strings-attached Trac
install and it was a seamless upgrad
sense. I see no reason to change the plan.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
it's invalid HTML to begin with). Any chance
we could get it committed soonish?
Thanks!
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--
You received this message because you are subscribed to the Goo
up.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
&g
urity-related lists. I suppose the two could be combined, but I'd hate
to see a paid person in any way decrease the efforts of volunteers (or our
motivation to find such volunteers). Just my two cents.
Cheers
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Ca
n.
>
> --
> 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 unsubscribe from this group, send email to
> django-developers+uns
go users with a relatively
insurmountable quantity of deprecated code. Frankly I'm not sure it's worth
it.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
--
You received this message because you are s
tinue to be wary of trying to
implement data constraints at the application level; that's something good
relational databases have been doing and improving upon for a long time and
I have little faith in my own capacity to reproduce or replace such
functionality.
Cheers,
Tobias
--
To
licitly requested by the developer, and it seems that validating
the model inside a form (whether fully or partially) breaks that contract.
Again - pardon my ignorance if there's something that I'm missing. I was
just alarmed to find a thread about forms + model validation given the
curren
I am by no means an expert on the matter, but I remember seeing a comment
awhile back suggesting that it generally makes more sense to fix the 2to3
script than to maintain two branches of the same library. Might that be the
case here as well?
Sent from a mobile phone, please excuse any typos.
On
oup/django-developers/browse_thread/thread/7904c7da7cb0085f/eb5a359e30307e89?lnk=gst&q=multidb+tobias#eb5a359e30307e89
If I recall correctly, the resolution was basically "not in this phase,"
i.e., this is something to be worked out in a future release of Django.
Tobias
--
or in Lisbon , Portugal.
> We are currently developing several web applications in Django and
> need someone to complete our team.
>
> I am sorry if this is inapropriate but it is not that easy to find a
> good Django developer via normal HR means.
>
--
Tobias McNulty
Caktus Consu
up.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
&g
the cookies documentation saying that it's "recommended to encode
cookies to avoid potential browser bugs," and list off a few of those bugs.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgrou
e need to make so that
it works more effectively:
http://docs.djangoproject.com/en/dev/internals/contributing/#ticket-triage
Cheers,
Tobias
On Mon, Oct 12, 2009 at 7:30 AM, Tobias McNulty wrote:
> In case it's not already on someone's radar, the patch on this ticket
> could use a review at some poi
s 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 unsubscribe from this group, send email to
>> django-developers+unsubscr...@googlegroups.com
>> .
&
com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 275
testing!).
Could someone with oracle knowledge take a look at this ticket? Given that
the "fix" introduces other issues in oracle backend, I hesitate to have this
committed before the oracle issues are resolved.
Thanks!
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro
+1
Sent from my mobile device.
On Jul 16, 2010 6:54 AM, "Carsten Reimer"
wrote:
Hello,
I am not quite sure if this is the right mailinglist but as long as my
remarks are about a core-component of django I hopefully chose the right
list.
Dealing with cache-stuff in Django I realized that it se
tell without seeing the patch. :-)
Could you stick it somewhere we can see it? Personally I like to see them
in Trac, since it comes with pretty colors. If there isn't a ticket already
out there for this I see no problem with creating one. We can always close
it if it gets rejected.
Cheers
Tobi
; group.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
e Google Groups
> "Django developers" group.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.goo
ob, so
> given the discrepancy I'm just curious whether it is in fact a design
> goal to have semantic parity between the backends shipped with Django.
>
Rejecting a particular subset of cache keys is also not the greatest analogy
to co-opting configuration values. :-)
Cheers,
Tobias
-
and I'd hate to
see innovation stifled at this stage by including one of the implementations
in contrib.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
USA: +1 (919) 951-0052
http://www.caktusgroup.com
--
You received this message because you are subsc
for all the other backends seems more like a
feature (and one that may require a lot more discussion, code, and testing
relative to the 1-line memcache fix).
Cheers,
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
USA: +1 (919) 951-0052
http://www.caktus
ll
suggests, it may be possible to enhance the admin in ways that make writing
third party apps like this easier.
Cheers,
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
USA: +1 (919) 951-0052
http://www.caktusgroup.com
--
You received this message beca
t; 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 unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com
>
uot;Django developers" group.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/dja
1 - 100 of 201 matches
Mail list logo
