Thank you Barhamou for raising the question here and starting the
discussion.
I agree with Adrian that this feels like a pretty niche use case.
Depending on the needs, other possible implementations might include:
4. A form field mapping to multiple model fields
5. A custom queryset/manager that
At Florian's suggestion in another thread, I propose that we move further
discussion of the settings refactor to the forum:
https://forum.djangoproject.com/t/settings-refactor/17352
On Wednesday, November 2, 2022 at 2:58:29 PM UTC-4 f.apo...@gmail.com wrote:
> The speckenv example highlights t
I started a forum thread on the settings refactor here:
https://forum.djangoproject.com/t/settings-refactor/17352
Regarding the original topic of this thread (
https://code.djangoproject.com/ticket/28236), are we ready to close this as
wontfix? I'm okay not proceeding with it (dj-database-url, dja
o those lists...)
Cheers,
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Mon, Nov 28, 2022 at 9:05 AM Carlton Gibson
wrote:
> Hey Roger,
>
> Indeed it does. You can set up Email Mode (that may not be the actual
> name) and it’ll work just like a mai
Hi Carlton,
Responses inline below:
On Mon, Nov 28, 2022, 2:40 AM Carlton Gibson
wrote:
> Hi Raphael, thanks for picking this up.
>
> Looking at the history here, particularly the discussion here
> https://groups.google.com/g/django-developers/c/UQjpzB39JN0/m/XGqdV8nbBwAJ
> but there are others
Hi Raphael,
Thanks for taking this on.
Starting with a limited scope seems like a good idea to me.
A couple other things I like about this approach:
- It tackles cache URLs at the same time (it makes sense for them to mirror
one another, IMO).
- No implicit usage of DATABASE_URL, but as you sai
Hi Pete,
A pluggable backend sounds like a good idea.
Regarding DJANGO_ENV, why not ship the template with two settings files and
use the existing DJANGO_SETTINGS_MODULE, instead of adding a new
environment variable?
Maybe that would be controversial too, I'm not sure, but perhaps less so
than i
Hi,
I also may be missing some context, but is this the mentioned package?
https://github.com/waveaccounting/dj-inmemorystorage
I have not used it, but it looks like a useful tool to have!
Tobias
On Thu, Oct 20, 2022 at 7:50 PM David Sanders
wrote:
> Hi,
>
> I may be missing some context her
Hi Yonas,
Thanks for sharing this list. Even so, in my opinion, this feature lives
best outside of Django where it can be appropriately customized as needed
for a given project.
I hope this helps.
Best,
Tobias
On Wed, May 11, 2022, 6:46 PM Yonas
wrote:
>
> Would syncing the block list from r
Tim,
Thanks for taking this on!
Needless to say, I'm all in favor of including a default 'users' app.
Adding one (as has long been recommended by the docs) is a task best
automated.
I've definitely had the "no the other folder" conversation more than enough
times myself. Personally I think I pre
Here's the incident report from Fastly:
https://status.fastly.com/incidents/vpk0ssybt3bj
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Tue, Jun 8, 2021 at 9:58 AM danushka padrushka
wrote:
> Hi Wadinga Leonard,
>
> I checked from diff
> Here is a great explanation of this exact issue, cleared it up for me:
> https://blog.jooq.org/2018/07/13/how-sql-distinct-and-order-by-are-related/
>
>
>
> On 28.10.2020., at 20:04, Tobias McNulty wrote:
>
>
> Hi all,
>
> Starting a thread on ticket #28560
> <
order_by() as-is, or not add "name" to the SELECT
in this case either?
>>> str(School.objects.values("county").order_by("name").distinct().query)
'SELECT DISTINCT "testapp_school"."county", "testapp_school"."name"
aise an
error if the list of columns in values() is insufficient to run the
requested query (i.e., never add a column implicitly if the user specified
a list of columns via values() or values_list()).
What do others think? What are other potential fixes I'm not thinking of?
Cheers,
Thanks for the report. The SPF record was updated today around 1:30pm EDT.
Please let us know if you continue to see issues.
On Thu, Oct 22, 2020 at 12:10 PM Adam Johnson wrote:
> Perhaps there's a task for the ops team to check the SPF/DKIM/DMARC
> records for djangoproject.com ?
>
> On Thu,
en as someone who does not self-identify as a Redis enthusiast.
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" g
you should inspect the
created migration BEFORE running `manage.py migrate` to ensure it does what
you expect. Press Y to continue or N to cancel." (needs copyediting of
course)
It would be easy enough to bypass with --no-input if someone doesn't want
the interruption.
Cheers,
*Tob
Tim your point is well made. I'm left with the feeling that an imperfect
convention is really not so bad, and possibly not worth the huge number of
global developer hours it would cost to effect such a change.
Plus (I make this argument mostly in jest), the new names, because they are
more Python
to any Django version beyond 2.1. I even thought about forking
>> Django and reverting this definition myself, but I prefer if Django itself
>> will do it then for me forking Django. If I work Django I might not be able
>> to apply all the changes you make in future releases, incl
e updated; i.e., it's simply a matter of timing that it
happened to break with Django 2.2.
There is some sample code in the ticket which might be good to try, to see
if it fixes the issue for you:
https://code.djangoproject.com/ticket/30439#comment:7
Cheers,
*Tobias McNulty*Chief
On Wed, Oct 30, 2019 at 12:29 PM Carlton Gibson
wrote:
> That _highly recommend_ sentence could go:
>
> > We highly recommend and only officially support the latest point release
> of each support Python series.
>
👏 Love it! (though perhaps drop or edit the second "support")
Tobias
--
You re
*, but I'm still not entirely sure about that. (The
other possibility being that that language is a holdover from the time when
we were supporting both Python 2 and 3.)
Cheers,
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Wed, Oct 30, 2019 at 10:56
I think it's a great idea.
On Thu, Jul 18, 2019, 12:46 PM Jacob Kaplan-Moss wrote:
> Hi folks -
>
> I’d like to gauge interest in adopting dj-database-url
> (http://github.com/jacobian/dj-database-url) as an official project
> (
> https://github.com/django/deps/blob/master/final/0007-official-pr
On Wed, May 1, 2019 at 8:56 AM Florian Apolloner
wrote:
> On Saturday, April 27, 2019 at 7:26:58 PM UTC+2, Carlton Gibson wrote:
>>
>> Right now I just wanted to move it down the page.
>>
>
> By all means do so…
>
+1
> I vaguely remember talking to Jacob when I saw him last and his stance on
>
I'd be happy to try setting something up, but a quick search didn't turn up
any obvious choices.
In the absence of information to the contrary, I'd hazard a guess that we
still need the CLAs...
Tobias
On Sat, Apr 27, 2019, 1:26 PM Carlton Gibson
wrote:
>
> On 27 Apr 2019, at 18:51, Florian Apo
, IMO). I do feel there's a pragmatic solution in here
somewhere.
Best to all,
Tobias
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Fri, Apr 19, 2019 at 8:52 AM Tim Graham wrote:
> I'm sorry for establishing some (foolish?) guidelines t
There are plenty of use cases when this behavior wouldn't be desired, such
as editing the same model object with 2+ different model forms. Such a
pattern might be more common when editing an existing object, but isn't out
of the question for creating new objects, either (think of a multi-step
form
On Sun, Apr 14, 2019 at 3:11 AM Nick Sarbicki
wrote:
> Just going to say that one of the main frustration points I've had when
> making a contribution is having to fix small formatting errors (often minor
> things in docstrings which aren't _always_ consistent).
>
I constantly need to be reminde
On Sat, Apr 13, 2019 at 11:35 AM Herman S wrote:
> I've set up how this _could_ look depending on some configurables in Black:
>
> * Default config: https://github.com/hermansc/django/pull/1
> * Line length kept at 119: https://github.com/hermansc/django/pull/3
> * Line length kept at 119, no str
on't pass our own tests...
In any case, while this sounds like a non-trivial project with some
questions to work through yet, I too like not having to worry about code
formatting and don't have any real objections to this.
Cheers,
*Tobias McNulty*Chief Executive Officer
tob...@caktusgro
s own domain may actually be saving us a
good bit of bandwidth (previously each subdomain had its own /s/ prefix
from which an identical set of static files was served).
Cheers,
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Sun, Mar 31, 2019 at 3:08 PM T
Having thought about this a little more, I may have found in answer to my
own question. :-)
The reasoning would seem to be that, by overriding LANGUAGES but not
LANGUAGES_BIDI, you risk introducing an inconsistency between the language
code *format* in these two settings (a la LANGUAGE_CODE and th
I am curious, what is the reasoning behind disallowing LANGUAGES_BIDI from
containing languages not in LANGUAGES in the first place?
If as Matthias says it is never iterated over, I'm unclear what problems
this might cause, though I agree the fix is simple enough...
At least perhaps the last para
On Sat, Mar 30, 2019 at 7:32 PM Tom Forbes wrote:
> I’m a stats nerd, and I think I’m not alone on this list in that respect,
> would it be possible to share some more numbers after a week of usage? I
> would be interested in the total bandwidth used/saved, the global
> distribution of requests a
ack to the DB, you should add them to .only(). But in any case it protects
you from silently losing data by forgetting to include them in
update_fields (at the risk of generating extra queries if you forget to
include them in .only(), but at least you can see those and optimize them
away).
Consider
Agreed it's probably better to make the switch now, and I'd be fine without
a replacement shorthand alternative for --keepdb.
Cheers,
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Mon, Mar 11, 2019 at 8:19 AM Carlton Gibson
wrote:
> Th
irm or deny
most of these. They are HTTPS checks, and I believe the numbers represent
the time to connect and retrieve the page content (for
https://docs.djangoproject.com/en/2.1/).
Cheers,
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Mon, Feb 25,
erged in time?
Cheers,
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receivi
Also generally in favor. Is there a bot for such a thing? It would be nice
to get a reminder a week or two *before* the unassign happens, either to
prompt an update OR an early self-unassign (if the person is not in fact
working on the ticket anymore and just didn't remember it was still
assigned t
ge on docs.djangoproject.com responds in
> 800–900ms.
>
>
>
>
> On 24 February 2019 at 14:35:55, Tobias McNulty (tob...@caktusgroup.com)
> wrote:
>
> Hi Tom,
>
> Thanks for your message. I think we'll end up with Fastly since it would
> be free, but I'm waiting
ms global
>> invalidation which we can trigger on every deploy, and cloudflare has
>> something similar.
>>
>> On Sun, 24 Feb 2019, 00:00 Tobias McNulty,
>> wrote:
>>
>>> Hi all,
>>>
>>> An implementation question has come up regarding cach
ter cache time? And what's a good cache timeout
for such pages?
* How long are we comfortable waiting for *other* (not frequently updated)
pages to timeout, in the event they do change?
Tobias
On Fri, Feb 15, 2019 at 7:13 AM Tobias McNulty
wrote:
> Thanks for sharing the results.
>
> I d
240KB transferred, Finish: 947ms, DOMContentLoaded:
> 627ms, Load: 910ms
>
> Tested on Chrome with "Disable cache" checked, and no render issue was
> found.
>
> On Friday, February 15, 2019 at 2:09:09 PM UTC+11, Tobias McNulty wrote:
>>
>> Adam, is there anothe
e
>>>> artifacts from the djangoproject.com website. And we would like to
>>>> ensure that the TLS termination happens by us and not some random service
>>>> provider. After all, Django is used by enterprises that do have some
>>>> restrictions on
you're allowed to download software from.
>>
>> By handing over DNS to some CDN provider, we loose the ability to ensure
>> that happens.
>>
>> That said, if there's a CDN that works as a reverse proxy and doesn't
>> require us to hand over contro
For me it's the trust factor (allowing someone else to decrypt and
re-encrypt all our data). This may be less of an issue for the docs site,
*if* we don't have to assign DNS authority for the whole domain to the CDN
provider.
Tobias
On Wed, Feb 13, 2019, 7:47 PM Kye Russell I’ve been hearing th
On Fri, Nov 30, 2018, 1:03 PM Adam Johnson Tobias - using database updates isn't always viable. Also the system under
> test might need to take in the model instance, mutate it and execute its
> own save(), and then there's no way of rolling that back if the object
> wasn't deepcopy'd
>
Fair enou
Hi Simon,
Intriguing proposal! Thanks for bringing it up. This is certainly something
I've struggled with on older projects we've continued to maintain.
My first impression (and it may be only that) is that this seems a big
magical and potentially confusing, especially in the event the copy
opera
Personally, I like the simplicity and elegance of a single SECRET_KEYS
setting. It's also a good way to raise awareness that rotation is A Good
Thing to be doing anyways.
In any case, I second all of those who've already endorsed this idea. If I
can help, let me know.
Tobias
On Sun, Nov 18, 2018
Hello,
I don't think this is something Django can or should handle. You need to
make your change in smaller increments so it doesn't break.
The proper forum for discussing this is the Django users list (or IRC or
Google...).
Good luck!
Tobias
On Mon, Oct 1, 2018, 8:47 PM martin_x wrote:
> H
d my preference would be for a loud failure
(i.e., an exception rather than a log message) when this "strict" mode is
enabled. One can easily downgrade that to a log message when needed, less
so the other way around.
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www
behavior)? One could then use `.only()` or
`.values*()` to avoid fetching the related model, if needed.
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contr
hat will suffice. I don't recommend this because I
think existing Django developers would find it confusing, but technically
it would be possible to change or swap out instances of AnonymousUser via
middleware, too.
Lastly, this related ticket might be of interest:
https://code.djangoproject.com
t) see a reason to say no.
Tobias
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Mon, May 8, 2017 at 10:07 AM, Marc Tamlyn wrote:
> Yes, don't need that sorry.
>
> On 8 May 2017 at 14:40, Adam Johnson wrote:
>
>> I'm pretty
I probably won't have time to do that myself in the near
future, but I would be happy to serve as a reviewer.
Tobias
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Sun, Apr 16, 2017 at 5:47 PM, Info-Screen
wrote:
> Wouldn't it be possib
velopers.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-developers/CAC6Op19-0JeL8Jdcq70-pvwz%
> 2Bi2hfKtopEvihca_rGfH1DrPww%40mail.gmail.com
> <https://groups.google.com/d/msgid/django-developers/CAC6Op19-0JeL8Jdcq70-pvwz%2Bi2hfKtopEvihca_rGfH1D
n
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit https://groups.google.com/d
se cases.
Tobias
--
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiv
trouble of changing the default password hasher currently, so ideally
users would get a stronger nudge than they do now when it comes time to
deploy to production. Making a switch here also has the added benefit of
circumventing some of the concerns around increasing PBKDF2 iterations
<https:
, can we offer some
> suggestions about how to tell if your site receives sufficient traffic that
> you might be impacted? Did anyone notice increased CPU usage in past
> upgrades?
>
> On Tuesday, January 10, 2017 at 1:27:19 PM UTC-5, Tobias McNulty wrote:
>>
>> IMO this d
The important thing here is, this demonstrates that we cannot just
>>> assume that all Python 3 installs have a "fast" PBKDF2 implementation =/
>>>
>>> On Wednesday, January 4, 2017 at 11:33:17 AM UTC-5, Tobias McNulty wrote:
>>>
>>>> ...
&g
On Jan 7, 2017 11:41 PM, "Jeff Willette" wrote:
the specific case I am talking about deals with google analytics cookies,
which are different for every user and sent with the request. When
accessing request.user, I really only care about sessionid and csrftoken,
if present. So sending a vary by c
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@
ears old at this point, so some benchmarks or at least further
research may be in order...
Tobias
--
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contribut
p/django-developers.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-developers/CAFHbX1K_1dCLrMQm4cy0u1i1cnEzLJV%2Bb_1-
> p9n58ERV7%3Dghvg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
*Tobias McN
opulate initial blank forms but not to fill missing data from the form
> input?
>
I tend to prefer the more cautious approach, i.e., allow the application to
supply default values to the form if they're not included in the POST, but
it sounds like I might be in the minority.
Tobias
--
of items from a model uses a SQL SELECT
> > >>> passing a list of all attributes of model, but usually we only use a
> > >>> small set of them on *list_display* attribute.
> > >>>
> > >>> I solved this problem overriding the *queryse
substantial testing to make sure all the right events (e.g., renames and
closures) are caught appropriately. It's not as simple as adding a commit
hash to a ticket's history, esp. if we ever wanted to change the fields
that were brought over from GitHub.
Tobias
--
*Tobias
groups.google.com/d/msgid/django-developers/CAK8PqJESDrr05-1jJeTbz8UQ%3D%2BJXYHU88w1iGBBnby5czwwVSA%40mail.gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Gro
ning this way too.
Having a permanent helper (perhaps MiddewareMixin as you suggested) for
dealing with TemplateResponses certainly sounds like a win, too.
Tobias
--
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
--
You received this message because you a
more appropriately, "not rendering if you can avoid
it" (i.e., your first strategy)?
Tobias
--
Tobias McNulty
Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
Sent from my mobile.
--
You received this message because you are subscribed to the Google Groups
"D
To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this d
somewhat resilient would be
helpful both for Django itself and the broader community of 3rd party apps
and backends.
Thanks in advance for considering re-opening this ticket.
Best,
Tobias
--
Tobias McNulty, Managing Member
Caktus Consulting Group, LLC
http://www.caktusgroup.com
--
You receive
from about 9am to 3:30pm EST (UTC-5) each day and
Karen Tracey will be here for most of that time to help review and commit
our patches (thanks Karen!). :-)
Cheers,
Tobias
--
Tobias McNulty, Managing Member
Caktus Consulting Group, LLC
http://www.caktusgroup.com
--
You received this message b
a parallel sprint in your area. The DSF and/or PSF can help
reimburse for sprint expenses.
Thanks and I hope to see you here or in the #django-sprint channel on
Freenode!
Cheers,
Tobias
On Tue, Oct 4, 2011 at 3:57 PM, Tobias McNulty wrote:
> Hi All,
>
> We'd like to host anoth
mail
off-list if you have any questions about sponsoring.
Hope to see you there!
Cheers,
Tobias
--
Tobias McNulty, Managing Member
Caktus Consulting Group, LLC
http://www.caktusgroup.com
--
You received this message because you are subscribed to the Google Groups
"Django developers&q
t take
arguments, that also modify data? The only one that I found in the list I'd
initially proposed that can be called without arguments is as_view(), and
I'm not sure that really even needs protection. Maybe there's no need to
protect anything with alters_data / proxying?
Th
On Wed, Apr 27, 2011 at 9:31 AM, Luke Plant wrote:
> ... If you need to store
> infinity in a database column, it's better to know sooner that your
> database doesn't support it so you can find one that does.
>
+1
--
Tobias McNulty, Managing Partner
Caktus Cons
meet).
On the other hand, if we've all been living with a trivial bug since 1.0, we
can probably live with it for just a little longer, and backporting
certainly doesn't sound worth the potential risk of a regression.
Cheers,
Tobias
--
Tobias McNulty, Managing Partner
Caktus Consulting
of the product will include that fix.
What if the window for bug fixes was time boxed, so that bug fixes would be
back/forward ported as usual up until 1-2 months prior to a new stable
release (perhaps coinciding with the first release candidate)? This way at
least we have some semblance of a st
e subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
>
with the
contrib.messages framework can be accomplished by implementing a custom
storage, similar to the following:
http://code.djangoproject.com/browser/django/trunk/django/contrib/messages/storage/user_messages.py
Cheers,
Tobias
--
Tobias McNulty, Managing Partner
Caktus Consulting Group, LL
semantically
> the lack of a value for the field. However, True and False are equals;
> False is not the lack of a value."
Whoops, looks like I should have refreshed this thread before hitting send.
:-)
Tobias
--
Tobias McNulty, Managing Partner
Caktus Consulting Group, LLC
http://www.ca
he current behavior
of BooleanFields, should we also make all not-null IntegerFields default to
0?
Tobias
[1] http://docs.djangoproject.com/en/dev/ref/models/fields/#null
--
Tobias McNulty, Managing Partner
Caktus Consulting Group, LLC
http://www.caktusgroup.com
--
You received this message bec
On Dec 16, 2010 7:20 PM, "Christophe Pettus" wrote:
>
>
> On Dec 16, 2010, at 2:31 PM, Luke Plant wrote:
> > That being so, there is a case for arguing that
> > ForeignRelatedObjectsDescriptor should not retrieve objects where the
> > field pointed to is NULL - for consistency with the inverse ope
On Thu, Oct 21, 2010 at 11:58 AM, Jacob Kaplan-Moss wrote:
> On Thu, Oct 21, 2010 at 10:44 AM, Tobias McNulty
> wrote:
> > I think the issue is that the commit has already been made, and that
> doesn't
> > feel like the right time to anyone to submit an alternate prop
On Thu, Oct 21, 2010 at 11:01 AM, Jacob Kaplan-Moss wrote:
> On Thu, Oct 21, 2010 at 8:19 AM, Tobias McNulty
> wrote:
> > That thread's pretty old and doesn't really end on anything conclusive
> other
> > than "work has started". I do see that the patc
On Thu, Oct 21, 2010 at 8:54 AM, Dougal Matthews wrote:
> On 21 October 2010 13:41, Tobias McNulty wrote:
>
>> is there another mailing list thread or wiki page somewhere that follows
>> or summarizes the decisions that went into django.contrib.staticfiles? I
>> th
ns in
this thread.
Thanks,
Tobias
--
Tobias McNulty, Managing Partner
Caktus Consulting Group, LLC
http://www.caktusgroup.com
--
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...@goog
ntation. I do prefer this
to the potentially false sense of security that copying the object may
involve.
Tobias
--
Tobias McNulty, Managing Partner
Caktus Consulting Group, LLC
http://www.caktusgroup.com
--
You received this message because you are subscribed to the Google Groups
"Django
ld it be worthwhile,
at least, to make the behavior configurable?
Tobias
[1]
http://docs.djangoproject.com/en/dev/topics/db/queries/#updating-multiple-objects-at-once
--
Tobias McNulty, Managing Partner
Caktus Consulting Group, LLC
http://www.caktusgroup.com
--
You received this message becau
On Fri, Sep 17, 2010 at 8:27 AM, SmileyChris wrote:
>
> On Sep 11, 1:12 pm, Tobias McNulty wrote:
> > I may be missing something, but queryset.delete() seems oddly implemented
> in
> > Django. It does a select to get all the IDs to be deleted, and then
> deletes
>
On Sun, Sep 12, 2010 at 11:55 PM, Tobias McNulty wrote:
> At the DjangoCon sprint this weekend I setup Django on our CI server for
> OSS and had it reporting on builds in the #django-sprint IRC channel. Would
> that be useful to continue post-sprint, and should I have it report to the
Hey all,
At the DjangoCon sprint this weekend I setup Django on our CI server for OSS
and had it reporting on builds in the #django-sprint IRC channel. Would
that be useful to continue post-sprint, and should I have it report to the
#django-dev channel as well?
Cheers,
Tobias
--
Tobias McNulty
out there? Should I move it to
"Accepted" and proceed with trying to fix it (though it may be harder than I
think)?
Thanks,
Tobias
--
Tobias McNulty, Managing Partner
Caktus Consulting Group, LLC
http://www.caktusgroup.com
--
You received this message because you are subscribed
ersions it parses the last integer itself.
>
The patch looks reasonable enough to me and I'm excited about getting it in.
Have you tested it on Python 2.4, 2.5, and 2.6?
Cheers,
Tobias
--
Tobias McNulty, Managing Partner
Caktus Consulting Group, LLC
http://www.caktusgroup.com
--
You rece
uge mess of templates and lives a perfectly happy life outside the django
core.
Tobias
[1] http://code.google.com/p/django-treenav/
--
Tobias McNulty, Managing Partner
Caktus Consulting Group, LLC
http://www.caktusgroup.com
--
You received this message because you are subscribed to
#x27;t a problem that everyone has.
>
> * Even if it is a common problem, is something where there are many
> possible ways to solve the problem
>
+1 leaving navigation outside the core.
Tobias
--
Tobias McNulty, Managing Partner
Caktus Consulting Group, LLC
http://www.caktusgroup.com
age 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
> .
> For more options, v
but it is a
neat idea. Like you've been saying, Django trunk does a pretty good job of
staying stable as it is and things seem to get fairly well tested on an
ongoing basis, so I'm not sure it's an issue.
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O.
1 - 100 of 201 matches
Mail list logo
