Would it be reasonable to have a backend-specific hook to determine a
fingerprint, where that could be mtime or md5 or whathaveyou as long as
equality (or maybe ordering) works?
On Oct 8, 2012, at 10:23 AM, Alex Ogier wrote:
> On Mon, Oct 8, 2012 at 1:06 PM, ptone wrote:
> While git may be
If you use/monitor/graph metrics (the idea, not Coda's library, but that
would be good, too), I'd like to hear from you.
What sort of metrics, under what implementation, would be useful to you
operationally?
--
You received this message because you are subscribed to the Google Groups
"Django de
+1, this looks like a good change anyway and doesn't smell to me.
On Fri, Nov 16, 2012 at 6:09 AM, Daniel Sokolowski
wrote:
> I like this approach.
>
> From: George Hickman
> Sent: Thursday, November 15, 2012 7:27 AM
> To: django-developers@googlegroups.com
> Subject: Re: Class based views: A sta
For the record: It's bad timing for Idan. He lives in Tel Aviv which
is currently receiving intermittent rocket attacks. He may be a bit
slow to respond. ;)
Let's wish him and his family safety and the luxury of worrying about
django's admin in good time.
On Thu, Nov 15, 2012 at 7:23 AM, Victo
Please do not send recruitment emails to this mailing list. This is
your one warning. Repeating will result in you being banned from the
list.
On Fri, Jan 25, 2013 at 12:47 PM, wrote:
> We are looking for a Full stack engineer with strong python and django
> development skills. Our client is a
On Mon, Mar 4, 2013 at 1:34 AM, Aymeric Augustin
wrote:
> On 4 mars 2013, at 01:07, Shai Berger wrote:
...
>> The use of savepoints in Django apps so far has been very little, as far as
>> I know. One point
>> I'm unsure of is the interaction of savepoints with cursors, since querysets
>> are l
I'm not sure what you're referring to here - integrity, uniqueness,
and locking are handled at the individual query level - transactions
just cause locks to be held (if needed) until commit or rollback. Can
you give a concrete example of an exception being raised at commit
time?
On Tue, Mar 5, 2
I, for one, would prefer that we not recommend TransactionMiddleware
so highly. Now that I'm doing active development with Rails, it's
quite clear to me that a major difference in the ORM layers are which
DB they grew up with -- the django orm is tuned best to postgres,
while working passably on m
It sounds like we need a way to tell the worker that we are done sending
requests to it so that the worker can do cleanup (of which db conn close is one
task). This mirrors the previous request_finished "coupling" to
requests_finished.
(OS?) Signal? Sentinel queue/socket/named pipe + backgroun
I'm not sure what you mean by "maps to".
The basic signal framework is in django.dispatcher. If you're
implementing https://code.djangoproject.com/ticket/11398 then you
probably want to import: from django.dispatcher import Signal.
django.db imports django.core.signals because it is a *consumer*
Hey all,
I've just created django-core-mentorship[1] with founding members
including Carl Meyer, Jacob Kaplan-Moss, Simon Charette, and Russell
Keith-Magee.
Modeled after pythonmentors.com, the intention is to help more
people make the leap from using django to contributing to it. It is a
com
Ahem:
[1] https://groups.google.com/forum/?fromgroups#!forum/django-core-mentorship
:)
On Wed, Apr 3, 2013 at 11:44 AM, Jeremy Dunck wrote:
> Hey all,
> I've just created django-core-mentorship[1] with founding members
> including Carl Meyer, Jacob Kaplan-Moss, Simon Charett
"easy" is for people new to contributing django or to open source in
general. Your view of "easy" may be different than our intended
meaning. :)
On Mon, Apr 8, 2013 at 2:58 PM, Lennart Regebro wrote:
> On Mon, Apr 8, 2013 at 4:57 PM, Jacob Kaplan-Moss wrote:
>> Thanks, please let me know if you
I've just seen a documented example of this breaking things in the wild.
https://github.com/simplejson/simplejson/issues/37
I think we broke backwards-compat here - django 1.5.1. plus sentry
5.4.5 dies because django's own DjangoJSONEncoder depends on stdlib
json, but sentry (and lots of things)
ying to use something from the
> standard library with simplejson, which is obviously wrong.
>
> Alex
>
>
> On Thu, Apr 11, 2013 at 5:51 PM, Jeremy Dunck wrote:
>> I've just seen a documented example of this breaking things in the wild.
>>
>> https://github.c
ils.simplejson only
> being in a pending deprecation state, is broken.
>
> On Thu, Apr 11, 2013 at 9:22 PM, Alex Gaynor wrote:
>> When doing what? What do I need to do to trigger this?
>>
>> Alex
>>
>> On Apr 11, 2013 6:16 PM, "Jeremy Dunck"
After reading that ticket, I'm not sure what Alex and I are
disagreeing on. I was suggesting using django.utils.simplejson
internally until it's removed, so that at least people could be
consistent with django itself. That way, DjangoJSONEncoder would be a
simplejson.JSONEncoder (if simplejson is
Thank you, Tim, for shepherding this.
On Jan 3, 2015 8:09 AM, "Tim Graham" wrote:
> Here is the fourth update with a week to go until alpha. At this time, I
> am thinking we'll have the feature freeze on Monday, January 12 as planned,
> but perhaps issue the actual alpha release a couple days lat
If getting proper support for other template backends would only delay the
1.8 release timeline by a couple weeks, I think that is preferable to a
generalized 1.8 backend which only include DTL until 1.9.
What do others think?
On Sat, Jan 3, 2015 at 3:23 PM, Aymeric Augustin <
aymeric.augus...@p
I suspect you have 2 different definitions of the signal under different
import paths. Ensure your python path doesn't have overlapping
directories, and that your signal imports refer to the same sys.modules key
(e.g. some_app.signals.foo all over, not proj.some_app.signals.foo and
some_app.signal
On Wed, Aug 25, 2010 at 6:16 AM, buddhasystem wrote:
>
> Does Django native caching only work when a template is rendered? If I have a
> view that just serves data wrapped in HttpResponse -- will it cache? In my
> experience, it won't -- why? Thanks so much.
You've mailed the django-developers l
On Thu, Sep 2, 2010 at 9:03 AM, Russell Keith-Magee
wrote:
...
> Effectively, this means that official support for Django under Python
> 3 is still a couple of years away.
Fortunately, there is plenty to do preparing for this glorious day --
many commonly-used libraries which Django depends on di
On Sep 4, 2010, at 11:45 AM, Russell Keith-Magee
wrote:
> On Thu, Sep 2, 2010 at 4:25 PM, Waldemar Kornewald
> wrote:
>> How often should I ping, so my patch won't be forgotten? :)
>
> Look - I don't want to appear rude or disparaging, but it will happen
> when it happens.
>
> Your patch is
http://www.scribd.com/doc/37113340/Why-Django-Sucks-and-How-we-Can-Fix-it
Presented here without comment, except that video of will be available
(probably on blip.tv) in (hopefully) a few weeks.
--
You received this message because you are subscribed to the Google Groups
"Django developers" gro
On Thu, Sep 16, 2010 at 6:36 AM, David Reynolds
wrote:
> Hi,
>
> I would really appreciate some feedback on this.
David, thanks for following up on this. You were unlucky in reporting
this issue during DjangoCon, so most attention has been elsewhere.
I've left comments (and a couple patches) on
Oleksandr,
I've forwarded this to django-developers@googlegroups.com which is
the more appropriate forum.
Please join that list to participate in the discussion.
On Wed, Sep 29, 2010 at 8:31 AM, wrote:
> From: Oleksandr
>
> Please change Ukrainian locale form uk to ua
> ua - is right
> uk
On Fri, Oct 1, 2010 at 1:41 PM, Gabriel Hurley wrote:
...
> In both cases, once that's done you can either write/help write a
> patch that has the desired effect, make sure it has docs and tests,
> test it on your own systems/projects, give feedback on the ticket...
> if you're certain it meets al
On Wed, Oct 6, 2010 at 8:12 PM, Mathieu Leduc-Hamel wrote:
> Greetings Django Developers,
>
> We, Montréal-Python, are the coordinators of the Python track at
> ConFoo 2011 and we are very proud to announce our call for speakers.
>
> PHP-Québec, Montréal-Python, Montreal.rb, W3Qc, and OWASP Montré
On Fri, Oct 8, 2010 at 2:36 AM, Russell Keith-Magee
wrote:
...
> Also, are there any API-level discrepancies remaining that need to be
> considered? The earlier django-dev thread suggests that there are some
> problems with get_multi(), but it also says that they've been fixed.
> Is this the case?
On Sun, Oct 10, 2010 at 4:41 PM, Jacob Kaplan-Moss wrote:
> Hi Laurent (and everyone else paying attention) --
>
> I'm currently working on redoing the community pages so that folks
> like you can add their own feeds without needing to go through me or
> anyone else. I should have that done here s
On Sun, Dec 19, 2010 at 2:55 PM, Yo-Yo Ma wrote:
>
> From the core team, are there any reliable clues to detect Django that
> are more consistent than naming conventions? CSRF doesn't
> always apply. This tool can also be helpful for those contributors who
> run Django showcase sites, etc.
Many
On Mon, Mar 28, 2011 at 3:36 PM, Jacob Kaplan-Moss wrote:
...
> PS: 66,045 lines of code plus 51,174 lines of tests.
Yes, but how many lines of docs? :-P
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
On Tue, Mar 29, 2011 at 11:11 AM, Carl Meyer wrote:
> Hi Jordan,
>
> On 03/29/2011 11:40 AM, Jordan MacDonald wrote:
>> I have three models, structured like so:
>>
>> Document
>> -Presentation
>> -Spreadsheet
...
>> I'd like to be able to write
>> Document.objects.all(). I'd then like to be able
On Tue, Mar 29, 2011 at 11:40 AM, Carl Meyer wrote:
> On 03/29/2011 12:40 PM, Jeremy Dunck wrote:
>> What about keeping abstract inheritance in this case, but allowing
>> Document.objects.* to work by returning instances of the subclasses.
>> Filtering, etc. would only work
On Thu, Mar 31, 2011 at 1:47 PM, Rajendra Pondel wrote:
> Hi i m new to dejano?
>
> where can i find what it is?
Please direct questions like this to django-us...@googlegroups.com.
You can find documentation here: http://docs.djangoproject.com/en/1.3/
--
You received this message because you a
On Thu, Mar 31, 2011 at 2:02 PM, Patryk Zawadzki wrote:
...
> Rather simple fix to the signal handler:
>
> def on_something_saved(sender, instance, created, **kwargs):
> if not kwargs.get('raw', False):
> do_stuff()
Concur, if the handler shouldn't run on loaddata, checking raw is the
r
On Wed, Apr 20, 2011 at 3:32 PM, Markus Gattol wrote:
> That's certainly a move in the right direction so +1 from me too. The
> problem of
> backporting correlates with how much time passes between any release
> i.e. long time between releases gives bigger pita with backporting.
> Even more so bec
On Wed, Apr 20, 2011 at 5:14 PM, TiNo wrote:
> First of all, this sounds like a nice idea.
>
> On Wed, Apr 20, 2011 at 23:25, Jacob Kaplan-Moss wrote:
>>
>> It takes me about 5 minutes to review most unreviewed tickets
>
> It takes me, being a newbie at reviewing tickets, quite some more time.
>
On Mon, May 2, 2011 at 9:54 AM, Carl Meyer wrote:
...
> I don't mind leaving get_profile() around, I guess, but IMO the best
> argument that can be made for that is "it's useless but mostly harmless,
> and it's not worth making people change their code to remove it." I'll
> continue to recommend i
On Thu, May 5, 2011 at 5:57 PM, Alex Gaynor wrote:
...
>
> Another option (which I haven't though much about). Is a button on trac to
> spot check a patch with this. When I start to look at a ticket a 1-click
> way to check if the patch is even going to apply is a low-effort way to let
> me know
In general, the TestCase does a good job of cleaning up the
environment (resetting the DB, etc.), but I've run across an edge case
that might be worth putting upstream.
I have a large codebase running multi-tenant -- lots of sites per WSGI
process, running process-per-request, and it serves those
On Tue, May 17, 2011 at 9:16 AM, Jonas H. wrote:
> Invalidation is what I'm unsure about too -- multiple ideas came to my mind,
> all involving some sort of Great Hash(tm):
Even within a single test command run, the same DB setup and same
fixture loads are done many times (for a sizable suit
On Tue, May 17, 2011 at 10:24 AM, Ned Batchelder wrote:
> Maybe it wouldn't be so bad to punt on invalidation? The cached databases
> would only have to be rebuilt if the models changed or if the fixtures
> changed, right? We have a similar situation now with migrations: you have
> to write one
On Fri, May 13, 2011 at 10:10 AM, Jannis Leidel wrote:
...
> I've added something related the other day in changeset 16165.
>
Following up here, Jannis added a patch to a sort-of related ticket:
http://code.djangoproject.com/ticket/15561
This refactors the context manager into also supporting us
On Tue, May 17, 2011 at 11:01 AM, Jannis Leidel wrote:
>> I was looking more for transaction rollback semantics -- rather than
>> overriding (and then restoring) specific settings, I was hoping for
>> settings to be set back just as they were before the test.
>
> Yah, but the good news is that the
On Tue, May 17, 2011 at 12:59 PM, Jonas H. wrote:
> On 05/17/2011 04:48 PM, Jeremy Dunck wrote:
>>>
>>> 1) Use file modification timestamps for all model and test related files.
>>> Advantages: simple, works.
>>> Disadvantages: Triggers cache invalidatio
On Tue, May 17, 2011 at 6:46 PM, Erik Rose wrote:
>> Is there a sensible to way "copy" databases in SQL?
>
> SQL 2003 introduced CREATE TABLE x LIKE y for cloning the schema of a table.
> It's supported in MySQL at least. You could then do a bunch of INSERT INTO
> ... SELECTs if you deferred for
I was wondering how people would feel about template origin being an
attribute of the Template instance.
The point to me would be to make it easier to see which location a
template is coming from; I think the compile_string func could do it--
after constructing the template, the loader would annot
On Tue, May 24, 2011 at 12:14 PM, Carl Meyer wrote:
> On 05/24/2011 11:53 AM, Jeremy Dunck wrote:
>> I was wondering how people would feel about template origin being an
>> attribute of the Template instance.
>>
>> The point to me would be to make it easier to see whic
Referring to Django's support for sitemaps:
https://code.djangoproject.com/browser/django/trunk/django/contrib/sitemaps
https://docs.djangoproject.com/en/1.3/ref/contrib/sitemaps/
In addition to the standard sitemaps, Google also specifies some extensions:
http://www.google.com/support/webmasters/
On Wed, Jun 29, 2011 at 3:55 PM, Simon Riggs wrote:
...
> I'm not sure I like your ORM syntax to generate that though. Why not
> just pass through the case statement directly? That way *any* legal
> CASE statement can be used, without inventing new ORM syntax each
> time.
Tables get aliased depen
On Thu, Jun 30, 2011 at 3:51 PM, Michael Blume wrote:
> First of all, I find it mildly odd that the context processor takes
> precedence over the variable explicitly set, but that's obviously arguable.
> Would it be possible for Django to kick up some kind of warning in cases
> like this, at least
On Fri, Jul 1, 2011 at 10:54 AM, Jim D. wrote:
> This issue came up again for me recently: Because the cache is not reset or
> flushed after every test, cache values linger there. This can create
> headaches when writing tests.
> I would like to propose that we treat the cache backend(s) like data
On Fri, Jul 1, 2011 at 12:27 PM, Jim Dalton wrote:
> Awesome feedback, thanks.
>
> On Jul 1, 2011, at 10:01 AM, Jeremy Dunck wrote:
>
...
>> If I were to do this, I wouldn't have cache shared between tests or
>> environments, so I'd be tempted to use flus
You've mailed the django-developers list which is for development *of
Django itself*. The proper mailing list about using Django is
django-users. Please send this message to django-users unless you're
proposing a change to Django.
http://groups.google.com/group/django-users
On Sun, Aug 28, 20
On Fri, Sep 2, 2011 at 11:04 AM, Ian Clelland wrote:
> I'm seeing errors which I believe are due to a race condition in
> django.db.models.query.get_or_create, on a fairly high traffic site. Our
> production servers are running Django 1.2.5, but I don't see any changes in
> the code in trunk that
> On Fri, Sep 2, 2011 at 11:22 AM, Jeremy Dunck wrote:
>>
>> On Fri, Sep 2, 2011 at 11:04 AM, Ian Clelland wrote:
>> > I'm seeing errors which I believe are due to a race condition in
>> > django.db.models.query.get_or_create, on a fairly high traffic site.
On Sun, Sep 11, 2011 at 11:56 AM, Joshua Russo wrote:
> I've wondered this for a while, but is there a reason why the call to
> admin.site.register(([Model], [ModelAdmin]) is not done within the init of
> ModelAdmin?
You can run multiple AdminSite instances mounted at different URLs.
admin.site i
Currently, calling select_related causes the QS to forget previously
added fields. Also, it seems that depth calls are not forgotten.
For example, cribbing from the tests here:
https://code.djangoproject.com/browser/django/trunk/tests/modeltests/select_related/tests.py#L129
If this:
Species.obj
On Tue, Sep 20, 2011 at 9:00 AM, Jim D. wrote:
> https://code.djangoproject.com/ticket/16245
I've looked at the patch and it seems good to me.
I have a suggestion:
Rather than (receiver, err, traceback), why not (receiver, exc_info)
where exc_info is the triple returned by sys.exc_info()? Ther
On Tue, Sep 20, 2011 at 12:09 PM, Jim D. wrote:
> Awesome, great suggestions both. That's a cleaner API and the implementation
> itself is even slightly cleaner.
> I updated the patch and uploaded it to the ticket. If you or anyone else
> wants to review it and ideally move it forward, that would
On Tue, Sep 20, 2011 at 2:16 PM, Carl Meyer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tuesday, September 20, 2011 1:26:22 PM UTC-6, jdunck wrote:
>> Well, I meant to mark accepted as endorsement of the patch, but that
>> made me owner.
>
>> I can't own it since I'm not a
On Wed, Sep 28, 2011 at 3:36 AM, Paul McMillan wrote:
> I'm Paul, one of the core devs for Django. I'm curious which class
> you're enrolled in and what your requirements are. I'm always excited
> to see new people looking to get involved in the project, and I happen
> to be VERY local.
Hi Paul &
It is indeed a bug.
On Fri, Oct 7, 2011 at 10:19 AM, Guilherme Salgado
wrote:
> Hi there,
>
> That function uses .objects on whatever model is passed to it by
> update_object() (or delete_object()), and I can't think of a reason to
> use that instead of the default manager (although my knowledge
How about:
http://web.archive.org/web/20110726001211/http://diveintopython.org/
?
On Wed, Oct 12, 2011 at 2:37 AM, rikuthero...@gmail.com
wrote:
> Hello,
>
> As described on the ticket [1], it seems that diveintopython.org is dead, so
> I changed every occurence for the mirror
> http://diveintop
On Mon, Oct 10, 2011 at 3:05 PM, Carl Meyer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
...
> 2. People write code that imports things inconsistently (sometimes with
> the project prefix, sometimes without it), and then when they go to
> deploy (without manage.py or setup_environ), th
On Sun, Oct 30, 2011 at 8:48 AM, Jim Dalton wrote:
...
> Anyhow, I honestly agree with you and Aymeric that a simple cache.clear() is
> fine, but I thought the CLEAR_BETWEEN_TESTS flag was a good way to answer any
> objections that we should be cautious about clearing the cache. If there are
>
On Sun, Oct 30, 2011 at 4:19 PM, Jeremy Dunck wrote:
> On Sun, Oct 30, 2011 at 8:48 AM, Jim Dalton wrote:
> ...
>> Anyhow, I honestly agree with you and Aymeric that a simple cache.clear() is
>> fine, but I thought the CLEAR_BETWEEN_TESTS flag was a good way to answer
>>
On Fri, May 30, 2008 at 5:16 PM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> Let's discuss the ORM save() method. In my opinion, unless I grossly
> misunderstand what's going on it seems the save method is very
> magical.
>
> First, some confirmations; The save method will INSERT a row into t
On Tue, Jun 3, 2008 at 2:58 PM, Joe Bowman <[EMAIL PROTECTED]> wrote:
> Should I just create it and
> tell people to copy it into the directory with the default cache
> backends? That appears the only way to insert a new one, but I'm so
> new to Django I thought I should ask first and see if
On Sat, Jun 7, 2008 at 7:23 PM, Rob Hudson <[EMAIL PROTECTED]> wrote:
...
> Where I work we use 0.96 (though I use trunk on my personal projects).
> We use 0.96 because we have up to 12 separate Django projects
> rotating through at a time
In that environment, perhaps you should work on tools an
On Sat, Jun 7, 2008 at 6:17 PM, James Bennett <[EMAIL PROTECTED]> wrote:
...
> Newforms-admin needs to get done. ... If that means organizing a sprint or
> two on it
> and then doing a trunk merge to get more eyeballs on the code, then
> let's do that instead.
As someone who would benefit from N
On Mon, Jun 9, 2008 at 11:37 AM, Rob Hudson <[EMAIL PROTECTED]> wrote:
...
> When our projects are done, they're done.
Ah, that's a foreign concept to me. In that case, yeah, your strategy
sounds good. :)
...
> Please tell me more about the legacy problem you are predicting.
>
Our projects ar
Where I'm from, exactly 1 is singular, and anything else is plural.
>>> from django.template.defaultfilters import pluralize
>>> pluralize(1)
u''
>>> pluralize(2)
u's'
So far so good.
>>> pluralize(1.1)
u''
That looks like a bug to me.
The trouble is here:
if int(value) != 1:
That's rounding
On Wed, Jun 11, 2008 at 5:17 AM, Patryk Zawadzki <[EMAIL PROTECTED]> wrote:
...
> It starts to get ugly if you consider languages such as pl_PL. For
> example "computer" in Polish:
>
> * 1 komputer
> * 2 komputery
...
Patryk,
While I am dimly aware that pluralization is often more involved
than
On Tue, Jun 10, 2008 at 11:33 PM, Gary Wilson Jr. <[EMAIL PROTECTED]> wrote:
>
> Nicolas E. Lara G. wrote:
>> I was wondering if there was some sort of design decision on this or
>> was just not implemented (yet).
>
> I would say it just hasn't been implemented yet.
I note that ValuesQuerySet.ite
I'm just guessing, but I think git-clone doesn't pull in remotes, so
that our clones are getting whatever's your master, hence trunk.
You can make a local copy of a remote branch like so:
git-checkout -b local/branchname branchname
There's no magic in the "local" prefix, it's just to distinguish
On Thu, Jun 19, 2008 at 5:02 PM, Rob Hudson <[EMAIL PROTECTED]> wrote:
>
> On 6/19/08, Rob Hudson <[EMAIL PROTECTED]> wrote:
>> Use the `-T`, `-t`, `-b` flags, or `-s` if the project has a "standard
>> layout". This should bring over branches and tags as well.
Oh, er, uh, I didn't notice only t
On Wed, Jun 25, 2008 at 11:24 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
...
> I don't know that it'll make it in before 1.0 since we're focusing on
> stuff on the roadmap, but if you're willing to be patient this'll
> almost certainly go in after. And possibly before if I find the time,
> b
On Wed, Jun 25, 2008 at 5:10 PM, Alex Ezell <[EMAIL PROTECTED]> wrote:
>
> I'd like to offer one more perspective. Magus- (Collin) was one of the
> first folks to help me in the IRC channel. And, initially, I did think
> to myself "well, that's a little smug."
>
> Then, I tried helping people the
I was thinking the FormWizard should allow GET to be used on all but
the last step, or should allow configuration of what to method to use.
Forms aren't just for posting.
Any interest in this?
--~--~-~--~~~---~--~~
You received this message because you are subscr
Wow, we're a bit quick on the draw, huh? :)
On Jun 30, 2008, at 21:39, Malcolm Tredinnick <[EMAIL PROTECTED]
stick.com> wrote:
>
>
> On Tue, 2008-07-01 at 10:31 +0800, Simon Li wrote:
>> Hi Guys;
>>
>> I use Django newforms,I met a problem
> [...]
>> I want to get ride of the , could you gu
I just ran into the same issue several people before me have:
Paginator is a bit dangerous when handed a queryset, and
QuerySetPaginator should be used instead.
This ticket exists, but no core dev has contributed to discussion yet.
http://code.djangoproject.com/ticket/7478
I'd like to avoid maki
On Tue, Jul 1, 2008 at 4:40 PM, David Cramer <[EMAIL PROTECTED]> wrote:
> - Is there a setting (e.g. settings.py) to restrict the maximum file
> size in an upload?
FILE_UPLOAD_MAX_MEMORY_SIZE
--~--~-~--~~~---~--~~
You received this message because you are subscrib
On Mon, Jul 7, 2008 at 12:12 PM, digitalxero <[EMAIL PROTECTED]> wrote:
>
> On Jul 7, 11:09 am, digitalxero <[EMAIL PROTECTED]> wrote:
>> *Adding this info to the ticket as well
>
> Well Trac decided I was spam and wouldn't let me post the data
Log in to trac.
See discussion here:
http://groups.g
I was using HttpResponse.set_cookie for the first time and annoyed
that expires has to be a properly-formatted string.
Why not take a datetime and do the formatting in the function?
Obviously this is a breaking change, unless we have an isinstance for
backwards incompatibility.
Thoughts?
--~--
On Tue, Jul 15, 2008 at 6:56 PM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
>
>
> On Tue, 2008-07-15 at 18:49 -0500, Jeremy Dunck wrote:
>> I was using HttpResponse.set_cookie for the first time and annoyed
>> that expires has to be a properly-formatted string.
&g
On Tue, Jul 15, 2008 at 7:14 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 15, 2008 at 6:56 PM, Malcolm Tredinnick
> <[EMAIL PROTECTED]> wrote:
>>
>> Yeah, we should do something sensible if passed a datetime. Can you open
>> a ticket?
>
On Mon, Jul 21, 2008 at 10:49 AM, Marty Alchin <[EMAIL PROTECTED]> wrote:
> I certainly hope 1.0 alpha isn't about hitting the
> backwards-compatible limit yet, because if it is, #5361 has failed to
> make the cut in time. The way I understand it, we still have some time
> to introduce mild incomp
On Tue, Jul 22, 2008 at 9:10 AM, Michael Radziej <[EMAIL PROTECTED]> wrote:
>> the djangoproject.com domain does currently not work, even when you ask the
>> ns*.mediatemple.net directly, at least from Germany. Probably simply a
>> problem with their name servers.
>
> Ah, it is back. Sorry for the
On Sat, Aug 16, 2008 at 12:01 PM, Mike Scott <[EMAIL PROTECTED]> wrote:
> I'm -1. the permissions stuff is part of the auth app. It should dilute the
> models stuff. I'm sure theres a way using the generic relationship stuff to
> do a reverse relationship variable on whatever models you wish. But
On Tue, Aug 19, 2008 at 5:01 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
...
> The best way to send me code is by letting me know about your remote
> git repo. Or use git-format-patch and send me patches. I can't really
> spare time to help with git, but someone in #django-dev probably can
>
On Wed, Aug 20, 2008 at 8:08 AM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
...
>> Also because of this should 8399, trivial as it is, go up on
>> BackwardsIncompatibleChanges?
>
> Yes, it should. Hopefully Gary (Wilson) will see this and make the
> change, since it was his commit. It was no do
On Wed, Aug 20, 2008 at 10:01 AM, James Turk <[EMAIL PROTECTED]> wrote:
>
> Quite understandable that this isn't a priority by any means, ticket
> including patch is up here for posterity:
> http://code.djangoproject.com/ticket/8447
The patch was a bit off; it used iteritems in iterlists in test
Also django-assets
On Aug 20, 2008, at 21:57, lingrlongr <[EMAIL PROTECTED]> wrote:
>
> I think that will work well. Thanks! =)
>
> On Aug 20, 10:40 pm, Justin Lilly <[EMAIL PROTECTED]> wrote:
>> You may want to check out django-chunks. I'm pretty sure it does what
>> you are looking for.
>>
On Thu, Aug 28, 2008 at 6:42 PM, Graham Dumpleton
<[EMAIL PROTECTED]> wrote:
>
> Can someone give an update as to where Django 1.0 may stand in respect
> of multithreading issues.
>
> I note that all the links to tickets referenced in:
>
> http://code.djangoproject.com/wiki/DjangoSpecifications/C
On Fri, Sep 5, 2008 at 8:52 AM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 5, 2008 at 2:34 AM, David Cramer <[EMAIL PROTECTED]> wrote:
>>
>> Does the error message pretty easily let you figure out what's wrong?
>
> A problem I've seen with infinite recursion is that while it may manifes
OK, enough noise on the naming.
Let's talk about what it should be and what should be measured. :)
(I suspect some devs already have a sketch regarding this stuff.
Please share.)
Do we want it to result in one big number like python/Lib/test/pystone.py?
Do we want to provide hooks for apps to
Patch or ticket, please.
On Sep 10, 2008, at 3:52, zvoase <[EMAIL PROTECTED]> wrote:
>
> Hi Django developers,
> Usually, signal receivers are defined as functions and then connected
> to a specific signal via a function call outside of the defined
> function. This can cause clutter, it violat
On Thu, Sep 11, 2008 at 2:19 PM, Justin Fagnani
<[EMAIL PROTECTED]> wrote:
> This could be implemented easily by adding a __call__() method to Signal.
>
That's a win. Anyone against?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to th
301 - 400 of 577 matches
Mail list logo
