On Wed, Nov 24, 2010 at 3:01 PM, Paul McLanahan wrote:
> I need to call a function
> from a view that needs to be able to set messages and potentially set
> other cookies. I need the request object to set the messages, and the
> response to set the cookies. This is already confusing in my opinion
On Thu, Nov 25, 2010 at 6:05 PM, Yo-Yo Ma wrote:
> I was reading about the low level cache API, and I noticed that you
> could cache None (implied by the recommendation not to do so). It made
> me wonder if I could cache other Python-specific objects, like
> dictionaries, lists, ORM Model instance
Hi Russ --
On Sun, Nov 28, 2010 at 1:13 AM, Russell Keith-Magee
wrote:
> For your consideration, I present a patch to resolve #12815 and
> #12816, adding a TemplateResponse and a render() shortcut.
Good stuff.
A couple of things though:
* I'm really not a fan of "bake()" and ".baked" -- it rea
On Sat, Nov 27, 2010 at 1:55 AM, Tim Diggins wrote:
> wondering why ImageField doesn't rely on width_field and height_field
> (if present and populated) for the dimensions? (i.e. from ImageField's
> perspective these seem to be "write-only" fields).
>
> This seems pretty unperformant (moving to ri
On Thu, Nov 18, 2010 at 9:47 AM, Russell Keith-Magee
wrote:
> However, given the Unless Jannis is willing to downgrade his -1 to a
> -0, I think a BDFL judgement is called for here.
Let's go with {% with a=foo b=bar %}.
Jacob
--
You received this message because you are subscribed to the Googl
On Thu, Nov 25, 2010 at 7:46 AM, Russell Keith-Magee
wrote:
> However, that doesn't mean we're completely prevented from making
> change. We could make this change under two circumstances. Either:
[snip]
> b) We need to declare that the current behavior to be a bug. We can
> break backwards compa
On Tue, Jan 4, 2011 at 9:37 AM, Andrew Godwin wrote:
> So, I've been working with the new generic Class Based Views for the
> last few days, and come across a slight inconsistency in the ListView.
>
> If you specify a value for paginate_by, ListView happily returns a
> "page" object into the conte
On Tue, Jan 4, 2011 at 3:37 PM, Yo-Yo Ma wrote:
> What's with all the hostility here? I've heard about this from others.
Let's just stop this, right now. There's no hostility in Marty's tone
-- if you're reading that, then take the night off and come back to
django-dev tomorrow.
This discussion
On Fri, Jan 7, 2011 at 10:11 AM, Jonathan S wrote:
> Like {% include %} and {% extends %}, I think we can include two more
> template tags in Django's defaulttags for controlling the "render
> flow". Click the links below for a usage example.
>
>
> ** A {% macro %} template tag
> http://paste.poco
Hi folks --
I'm starting the switchover to the new djangoproject.com server right
now. Might be around 5 mins of downtime or so.
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@
On Fri, Jan 28, 2011 at 3:33 PM, Jacob Kaplan-Moss wrote:
> I'm starting the switchover to the new djangoproject.com server right
> now. Might be around 5 mins of downtime or so.
Migration should be complete now. I'm still cleaning up a few
last-minute things, but if you notic
On Fri, Feb 4, 2011 at 2:45 AM, Tai Lee wrote:
> It seems to happen with very small file uploads as well. I've seen it
> reported with 30KB uploads, while at the same time 60MB uploads work. If I
> can't find a problem with the server causing disconnects, and it is actually
> on the client side
On Mon, Feb 14, 2011 at 11:41 AM, Matteius wrote:
> No the hits are with the initial page load before any AJAX gets
> called, my AJAX code is 2 DB hits. I am not claiming select_related
> should be default, but somehow it should be an option for the admin
> change form.
Have you tried supplying
On Mon, Feb 14, 2011 at 11:51 AM, Matteius wrote:
> Also I must have filled out the Django EuroCon 2011 Amsterdam form 4
> or 5 times and I still haven't received any E-mails about this.
Hey, this (and the rest of your email) is pretty off-topic for this
list -- can you please try to keep the foc
Hi Tonton --
Yes, I changed the search on docs a few weeks back. It's far from
perfect, but I'm trying to improve it. Can you give me some specific
links to searches that aren't working for you?
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django develope
On Fri, Feb 18, 2011 at 7:04 AM, Will Hardy wrote:
> In case there's any confusion in the question, it appears as if adding
> a period or braces to a word makes it impossible to be found, even
> when the exact string exists in the documentation:
>
> * http://docs.djangoproject.com/search/?q=get&re
On Mon, Feb 21, 2011 at 3:23 PM, poswald wrote:
> Russ, Carl, thanks for your feedback. Russ, I understand what you say
> about not wanting to adopt crypto code because of the additional
> responsibility. Unfortunately, there aren't very good options. Django
> contrib.auth already makes the recomm
Hi Rohit --
I had a skim of the document, too, and my feelings are pretty close to
Russ's, so I won't bother with any specific feedback -- he basically
speaks for me, too.
To build off Russ, though, I have a bit of a meta meta-suggestion
about OWASP in general. One huge problem I have as a softwa
On Thu, Feb 24, 2011 at 4:59 PM, mmcnickle wrote:
> So there you have it, we have a small regression in performance for
> the most common case use, and a huge potential gain for the less used
> (and some would argue, badly designed) query.
>
> What do you think, is the gain worth the hit? Is it po
On Sat, Feb 26, 2011 at 11:47 AM, Paul McMillan wrote:
> We need to either deprecate it, provide some validation, or fix the
> docs to say it doesn't do anything. We can't fix the docs till we have
> a decision on this ticket.
I say deprecate the field entirely. There isn't a good stdlib way to
v
On Tue, Mar 8, 2011 at 9:35 PM, bendavis78 wrote:
> I'd like to start a discussion on this since russelm closed the
> issue. There are a few other people that believe the issue should be
> left open. I've been using this patch for nearly two years, and have
> found it to be useful in several di
Hi Christophe --
Interesting; I didn't know about these constructs.
I'm not opposed to this change, but I am a bit concerned about opening
up the ability to use raw() for stuff like UPDATE/DELETE where it'd be
a nasty code smell. I'd be interested in your thoughts on that: is
there a way we can p
OK, I'm sold - let's just kill the "protection".
Christophe, can you write a patch including a new warning to put in the docs?
Thanks,
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-deve
Hi Vana --
This sort of thing is utterly unacceptable here. This is a technical
group dedicated to discussions of Django itself, not end-user stuff
and certainly not personal promotion. What you posted is really almost
spam, and if you've spent any time around technical folk at all you'll
know how
On Wed, Mar 16, 2011 at 4:24 AM, Johannes Dollinger
wrote:
> I would be nice if support for composite primary keys would be implemented as
> a special case of general composite fields. There would be no need for new
> Meta options:
>
> class Foo(Model):
> x = models.FloatField()
> y = mode
On Mon, Mar 21, 2011 at 2:33 AM, Christophe Pettus wrote:
> I'd like to make one more pitch for a slightly different implementation here.
> My concern with CompositeField isn't based on the fact that it doesn't map
> one-to-one with a field in the table; it's that it doesn't have any of the
>
Hi folks --
Thanks for the intro, Idan!
I thought I'd just fill in a few things from my point of view and give
a bit of background to this:
It turned out that quite a group of core devs ended up coming to PyCon
a couple weeks ago so we ended up having an impromptu lunch and
meeting. One of the t
On Wed, Mar 23, 2011 at 4:39 AM, Luke Plant wrote:
> It appears to me that this reports page is not nearly as useful as it
> could be, and I'm thinking of redesigning it.
Sounds just fine for me -- I really threw together the first version
with very little thought. Feel free to go ahead!
On a se
Hey Patrick --
On Wed, Mar 23, 2011 at 11:42 AM, pokecho wrote:
> I am writing to ask whether it is possible to configure
> "django.contrib.auth" so that it can implement Two Factor
> Authentication to step up login security.
This question's more appropriate for django-users, which is where
usa
Hi Patrick --
Look, I don't mean to be a jerk, but again this really should be
posted to django-users. Any question that begins "how can I..." or
"can Django..." isn't on-topic for this group. All of your questions
are on-topic for django-users and would probably get answers or at
least some point
Hi folks --
Lately I've been trying to think about a few ways that software might
help our user and dev community as both continue to grow. I have a few
things I want to try out as "spikes"
(http://c2.com/cgi/wiki?SpikeSolution) to see if they're really
viable.
I'm being deliberately vague here t
On Thu, Mar 24, 2011 at 6:44 PM, Luke Plant wrote:
> Have a look and anyone feel free to improve. For me, it has certainly
> flagged up the areas we are doing well and badly as core developers, and
> the areas where we shouldn't feel so bad.
This looks great to me, at least -- thanks!
Jacob
--
Wow, I got a lot more responses to this than I'd thought, so I'd say
I'm well on my way here. Thanks so much everyone -- y'all rock.
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develope
On Fri, Mar 25, 2011 at 6:45 PM, maxi wrote:
> Yes, that seems to be the problem. Firebird doesn't support deferred
> constraints.
> Are there any approach or workaround to solve this ?
No workarounds, no. We need to refactor our test suite to not rely on
deferred constraints (except of course wh
On Fri, Mar 25, 2011 at 10:43 PM, Alex Gaynor wrote:
> There's http://code.djangoproject.com/ticket/3615, most of the effort there
> has been on making MySQL not be stupid though :) Someone at PyCon told me
> they found a way to make it work though (Chris Adams I think?).
I dunno -- almost every
On Sat, Mar 26, 2011 at 6:31 AM, Graham Dumpleton
wrote:
> In short, it is all a mess and trying to provide support for it in one bit
> of code is possibly asking a bit much.
One possible solution would be to split the problem up a bit. Django
could provide an HttpFileResponse object. This would
On Sun, Mar 27, 2011 at 5:42 AM, -RAX- wrote:
> I am referring to this:
> http://docs.djangoproject.com/en/dev/releases/1.3/#filefield-no-longer-deletes-files
> Instead of preventing the data loss from happening a very usefull
> feature has been removed.
I'm sorry this caused an problem for you.
On Mon, Mar 28, 2011 at 12:56 AM, Julien Phalip wrote:
> Now that 1.3 has been released (yay!), I'm reviving this thread to see
> if we can make Trac a little more efficient on our way to 1.4. I'll
> try to summarise what's been suggested so far in regard to improving
> and clarifying the "Compone
On Mon, Mar 28, 2011 at 4:16 AM, -RAX- wrote:
> Said so I will start implementing such a maintenance job, and I am
> willing to share it so maybe we could include it in a future release
> of django.
Sounds good -- I look forward to seeing your code!
Jacob
--
You received this message because y
On Sat, Mar 26, 2011 at 8:45 AM, Waldemar Kornewald
wrote:
> That's pretty much exactly what django-filetransfers tries to do on
> the download side:
> http://www.allbuttonspressed.com/projects/django-filetransfers
> Hotever it's not only for X-Sendfile, but also for any other file
> serving mecha
On Mon, Mar 28, 2011 at 11:04 AM, Dan Fairs wrote:
> We don't have a core site base template. Each client on our system gets
> their own, as IA/branding etc. varies considerably (and indeed includes
> chunks of markup that the client supplies directly).
... and congratulations, you've successfull
On Mon, Mar 28, 2011 at 11:22 AM, Waldemar Kornewald
wrote:
> I do agree that it's too complicated (esp., the forms) and I plan to
> improve django-filetransfers in this regard. The biggest complexity
> comes largely from file upload handling (which I understand isn't a
> problem you're trying to
On Mon, Mar 28, 2011 at 1:13 PM, Waldemar Kornewald
wrote:
> That's a good goal and as long as you only focus on file downloads
> it's possible to reuse the middlewares setting. However, if you ever
> want to provide an abstract file uploads API we're back to the same
> problem.
I'm trying to tal
On Mon, Mar 28, 2011 at 3:29 PM, Andrea Zilio wrote:
> I was just wondering if anyone knows the total number of lines of code
> of Django.
Hi Andrea --
This question's off-topic for this list. Django-dev is for discussion
development of Django itself, and the length isn't really relevant. In
the
On Mon, Mar 28, 2011 at 4:08 PM, Julien Phalip wrote:
> I wouldn't mind trying but I don't have much experience administering
> Trac and I wouldn't want to make a mess. Earlier in this thread
> Gabriel has offered to help as he's got the Trac skillz.
>
> Gabriel, are you around? :-)
Sweet. I'll l
On Mon, Mar 28, 2011 at 4:19 PM, Luke Plant wrote:
> Proposal: remove compatibility fallbacks for short-lifetime signed data
> (shortening the deprecation process).
Sounds perfectly fine to me. Skipping versions is generally a dicey
idea anyway, so recommending a brief stop in 1.3 for people goin
Hi Mikołaj --
On Tue, Mar 29, 2011 at 8:45 AM, Mikołaj S. wrote:
> I've came up with an idea of improving default FOR template tag:
> {% for ... in ... %}
> By adding something similar to list comprehension syntax:
> {% for ... in ... if ... %}
Can you give us some context for this request? What
Hi Armin --
Can you speak a little more about how you'd see the workflow working
with this new library? It seems a bit complex to have a library that's
*copied* between Django and Jinja: I'd worry about patches getting
lost.
For context, this has happened a few times with the simplejson and
eleme
Sorry, but without a specific use-case I'm just not convinced.
Jacob
--
You received this message because you are 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
dj
On Wed, Apr 6, 2011 at 3:22 PM, trybik wrote:
> Hi Łukasz,
>
> On Apr 4, 8:43 pm, Łukasz Rekucki wrote:
>> It's best to report bugs on the tracker. Otherwise, they'll die in
>> infinite depths of everyone's mailboxes.
>
> that sounds like too much hassle for me. Please, feel free to report
> this
On Tue, Apr 5, 2011 at 7:45 PM, Michal Petrucha wrote:
> Anyway, I'll post at least the part I have already written so that at
> least something can be commented on for now.
So far this looks pretty good to me. Assuming you get the rest done
with a similar level of detail I'll be voting to approv
On Mon, Apr 11, 2011 at 12:27 PM, Amit Reks wrote:
> We have an opening for a Python Developer in San Jose, CA.
Amit, this is the second time you've posted off-topic unwelcome job
ads to this list. Don't do it again or I'll be forced to ban you.
Jacob
--
You received this message because you a
Hi Julien --
Thanks for your work on this! I'm working my way through the patch,
and it's looking good. I'm pretty happy with the internals, though I
do have some questions about the public API:
* I'm rather unhappy with the `SimpleListFilter`/`FieldListFilter`
breakdown, and especially the way `
Hey all --
I think I agree with Ned here: I can't see the downside to fixing it
on the release branch. "It violates our policy" doesn't count IMO:
it's *our* policy, and we get to break it if there's a good reason.
Making translation in JavaScript work is a good reason as I see it.
Jannis: can yo
Hi folks --
Over the past few weeks, the core development team have been
discussing how we can streamline our process to get more work done
quicker. It's pretty clear that the bulk of the community wishes
Django could move forward a bit faster [1], and we'd like to be able
to deliver more awesomen
Hi folks --
We have a chronic problem: our new ticket review queue. We get roughly
50 new tickets each week, and we typically don't keep up with this
flow very well. Eventually, someone (Hi, Russ!) takes it on himself to
review the massive backlog, but that's damned painful.
Right now we only hav
Dang it, I forgot the most important part: how to *find* tickets to review!
You can find a link to unreviewed tickets at
http://code.djangoproject.com/wiki/Reports (along with a bunch of
other cool canned queries).
Jacob
--
You received this message because you are subscribed to the Google Grou
Hi folks --
Just as a quick FYI, I added an official "Easy pickings" field to Trac
to replace the current keyword-tagging thing. I wanted something a bit
more obvious; figured it couldn't hurt.
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django developer
On Wed, Apr 20, 2011 at 5:14 PM, TiNo wrote:
> It takes me, being a newbie at reviewing tickets, quite some more time.
> Would you (or any other core dev / speed reviewer) mind sharing your
> workflow? Any scripts to create environments at certain revisions or
> something alike? Or to quickly run
On Wed, Apr 20, 2011 at 5:24 PM, Luke Plant wrote:
> Hmm, Jacob didn't specifically mention regressions, though in our
> discussions on django-core we did include them.
Yup, sorry - was moving too fast. Regressions, clearly, get backported
-- if something worked in 1.2, it should work in 1.3 unle
On Wed, Apr 20, 2011 at 5:44 PM, Carl Meyer wrote:
> So you don't necessarily reproduce it yourself before marking Accepted?
Mm, it depends. Sometimes I don't need to -- it's clearly a bug, and I
see everything I need to track it down. I generally trust that if the
user could be bothered to write
On Thu, Apr 21, 2011 at 8:05 AM, Aymeric Augustin
wrote:
> I reviewed 5 new tickets: #15782, #15792, #15793, #15795, #15798. I'd like
> someone to take a look at #14091.
Done - thank you! I left comments on the ticket.
Jacob
--
You received this message because you are subscribed to the Google
On Thu, Apr 21, 2011 at 8:13 PM, Michael Radziej wrote:
> If the bug is really bad or the fix looks simple, fix the bug. Else,
> close it as duplicate, but keep the tickets consistent for the users and
> promote the feature request to a bug ticket.
>
> Is this OK for you?
That's more or less how
On Fri, Apr 22, 2011 at 3:26 AM, Aymeric Augustin
wrote:
> I have retroactively added 5 tickets for Alex's review, plus 5 tickets that
> I'd like to trade against a review of #15255, especially the second comment.
Done!
BTW, I'm pretty sure Alex was joking about you needing to do five
more, so d
Hi Shawn --
FYI, we get updates to tickets sent over email (see the django-updates
group) so you don't need to ping here when you've updated something --
we'll see it either way :)
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To
On Mon, Apr 25, 2011 at 10:28 AM, Jonas H. wrote:
> I'd like you to look into http://code.djangoproject.com/ticket/15696.
Done. Unfortunately, the result's probably not what you wanted. If
you'd like to re-use your review wuffie I'd happily take a look at
something else instead; just let me know.
On Mon, Apr 25, 2011 at 11:09 AM, Stephan Jäkel wrote:
> Are there any doubts integrating django-formwizard into Django?
I'm +1 in theory. I need to spend some time going through your code,
and I'll need to see some documentation on porting existing wizards to
the new code (unless it's truly 100%
Hi xeed --
I'm sorry, but we can't help you. This list, django-developers, is for
discussion of Django development itself, not user questions.
If you need help using Django, please direct your question to the
django-users mailing list.
Thanks!
Jacob
--
You received this message because you ar
On Wed, Apr 27, 2011 at 2:44 AM, Conrad Calmez wrote:
> two weeks ago I started fixing the ticket #4287. It appears that
> infinity values can not be stored to FloatFields using MySQL (that is
> what I reproduced). I found out that MySQL can not handle infinity
> values. My Fix uses the minimal an
On Thu, Apr 28, 2011 at 6:32 AM, Waldemar Kornewald
wrote:
> As suggested by Russell, I'll try to explain the reasoning behind
> every proposed change on the wiki page in the next few days.
That would be a huge help. I'm trying to wrap my brain around the
megadiff Jonas posted, but I'm having tro
On Fri, Apr 29, 2011 at 3:57 AM, mcflurry7_11 wrote:
> I was wondering if any of you could help me out.
I'm sorry, but we can't. This list is really the wrong place for
messages like yours. First, this is a *Django* list and second this is
a list for *developers* of Django, not end user questions
On Thu, May 5, 2011 at 6:21 AM, Dave McLain wrote:
> I got frustrated with the number of patches that wouldn't merge with trunk,
> so like any sane person would at 2 in the morning I started writing a script
> that would screen scrape the Ready For Commit report, download the patches
> for every t
On Thu, May 5, 2011 at 8:06 AM, Patryk Zawadzki wrote:
> This problem is now more severe due to Facebook returning proxied
> e-mail addresses in this format:
>
> apps+111.22.abcdef0123456789abcdef0123456...@proxymail.facebook.com
Unfortunately, the problem of upgrading everyon
On Thu, May 5, 2011 at 9:08 AM, Yishai Beeri wrote:
> Wouldn't it be possible to work around this, even for the time being, by
> having auth.User read a SETTING to use as the default max_length (defaulting
> of course to the old 75)?
No, for any number of reasons. Primary because if you get it wr
Hi Bruno --
I'm sorry, but we can't help you here. This mailing list is for
discussion of developing Django itself, not user questions.
The django-users group is the right forum for questions like yours,
and I think you'll find an answer if you direct this question over
there.
Thanks!
Jacob
--
On Mon, May 16, 2011 at 7:36 PM, Erik Rose wrote:
> Toward that, should I work up a Django patch, or would the core team rather I
> release my work as a pluggable package?
Patch, please! Fast is good :)
Jacob
--
You received this message because you are subscribed to the Google Groups
"Djang
Hi Jannis --
Great work - thanks to both you and Stephan!
All in all this is fine to go in as far as I'm concerned, but I do
have a few nitpicky things that'd be nice to fix:
* There's a bunch of code in formtools/wizard/__init__.py (the legacy
wizard, right?). Generally I dislike having a bunch
On Tue, May 31, 2011 at 4:27 PM, Jannis Leidel wrote:
> This is needed to load the default template
> django/contrib/formtools/wizard/wizard_form.html. I could definitely
> add a note about it in the installation steps but see no way around
> it generally. Any other idea?
Ah OK, I missed that. Ne
Hi Idan et al. --
Thanks for putting this all together!
In general, I like this a lot, and I'm always going to defer to the
eyes of someone like Idan who spends more time wrangling templates
than I do. So I like the general gist, and I most don't mind the {%
formconfig %} business.
However, I do
Hi Jim --
Historically, most Django core developers have been PostgreSQL users
(and advocates to some degree). This has meant that, yes, MySQL
support has lagged behind. It's not that MySQL support isn't
considered important, but it is a matter of priorities. I, at least,
am going to prioritize th
On Mon, Jun 27, 2011 at 4:24 PM, Jim D. wrote:
> I spent some time last week and over the weekend nailing down a
> solution for https://code.djangoproject.com/ticket/3615 . This is the
> ticket about allowing forward references when loading data on the
> MySQL InnoDB backend. My patch implements t
On Mon, Jun 27, 2011 at 5:27 PM, Jim D. wrote:
> Does it work in production is a hard question for me to answer, if I
> understood your question properly. In my projects, I really only touch the
> loaddata command when I'm running tests (I guess loading data via
> initial_data.json into a producti
On Thu, Jun 30, 2011 at 1:38 PM, Daniel Swarbrick
wrote:
> Last year a customer's MySQL 5.1 server [...]
I doubt it was your intention, but this kind of argument can *so*
easily spiral into a flamewar. Certain things -- text editors,
monospace fonts, operating systems, database engines -- just ca
On Fri, Jul 1, 2011 at 12:07 AM, Victor Hooi wrote:
> Has there been any recent news?
If you watch the commit timeline
(https://code.djangoproject.com/timeline) you might have seen a
handful of UI cleanups that've done in over the past few months;
Idan's contributed to those. I can't recall 'em a
On Mon, Jul 4, 2011 at 12:13 AM, Ryan wrote:
> Umm... How about now?
Sorry, but this isn't going to happen. I left more information on the
ticket: https://code.djangoproject.com/ticket/6362#comment:43.
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django
On Mon, Jul 4, 2011 at 8:54 AM, Jim Dalton wrote:
> I've created a ticket for this and uploaded a patch:
> https://code.djangoproject.com/ticket/16401
> Please feel free to review and let me know if this is a good idea in the
> first place, as well as if the patch makes sense and is the right ap
On Mon, Jul 4, 2011 at 10:59 AM, Ole Laursen wrote:
> It sounds like you've never been bitten by strip bugs.
Then I must haven't been clear enough -- sorry -- because I certainly
have, many times. I've also found it incredibly easy to solve in my
user code: ``form.cleaned_data['field'].strip()``.
On Thu, Jul 7, 2011 at 8:37 PM, Tai Lee wrote:
> The docs say that when writing custom template tags, the `render()`
> function should never raise `TemplateSyntaxError`, [...]
This rule is the correct one, and I'm very much against changing it.
> [...] but some of Django's own template tags (e.g
On Thu, Aug 18, 2011 at 5:25 PM, Paul McMillan wrote:
> I added some test cases and cleaned the code up a bit. I believe sure
> this solution is backwards compatible (we're adding the string
> conversion, something that shouldn't have been possible before), but
> I'd like input from some other peo
On Thu, Aug 25, 2011 at 4:06 PM, Mikhail Korobov wrote:
> One thing I always like about django is how the community is peaceful and
> how the django itself is peaceful and engineer-minded, not marketing-minded:
> I can't imagine whydjangoisbetterthanx.com website bashing zend, rails,
> pyramid and
On Tue, Aug 30, 2011 at 2:33 AM, Idan Gazit wrote:
> So, a while back, I announced that Django is dropping support for IE6 in the
> admin. What I _didn't_ specify is what browsers are supported.
> I'm currently composing a bit for the 1.4 release notes about admin browser
> support, and wanted to
On Fri, Sep 2, 2011 at 4:15 PM, Greg Donald wrote:
> Clearly you've been working with some hybrid wanna-be designers who
> probably don't do any heavy lifting in either realm.
Greg, I hope and am going to assume you're joking. If not -- and
remember with email it can hard to tell -- this comes ac
On Sun, Sep 11, 2011 at 6:11 PM, Daniel Swarbrick
wrote:
> License? What license? Heheh... my PBKDF2 implementation is solely
> being used by an in-house Django app. I haven't open sourced it, but
> am perfectly willing to let you guys pick over the PBKDF2 class and
> include it in Django if you s
On Mon, Sep 12, 2011 at 3:44 PM, Carl Meyer wrote:
> Actually, I think there's generally consensus that requiring models.py
> is not ideal.
Yeah, that sounds about right. I get bitten by missing models.py all
the time, and I should supposedly know better. It's lousy usability,
so let's focus on g
Hi folks --
I agree 100% with what Russ had to say on the ticket: leaking
information about admin accounts isn't OK, and we won't change that.
If someone would like to submit a patch with different wording that
covers all cases -- "this is an invalid user/password for admin
access" or somesuch --
Hi folks --
I'd like to convert all the view decorators built into Django to be
"universal" -- so they'll work to decorate *any* view, whether a
function, method, or class. I believe I've figured out a technique for
this, but I'd like some feedback on the approach before I dive in too
deep.
Right
On Mon, Sep 19, 2011 at 9:16 PM, Carl Meyer wrote:
> The milestone field came up again in IRC discussion tonight between
> Julien and Paul and I -- namely, that it doesn't seem all that useful
> and causes noise in Trac.
I agree. I think the "release blocker" flag basically replaces the
milestone
On Wed, Sep 21, 2011 at 10:41 AM, Simon Charette wrote:
> http://lmgtfy.com/?q=vcvarsall.bat
C'mon, that's totally rude and really not OK.
If you have the time to answer someone's question then please do so,
but if you don't simply telling people to "google for it" or "RTFM" is
just impolite. "l
On Tue, Sep 20, 2011 at 4:17 PM, Paul McMillan wrote:
> Yes! Let's get rid of [the "accept" button]. It still confuses me now even
> when I
> know exactly what it means!
If anyone knows how to do this, let me know and I'll make it happen.
Jacob
--
You received this message because you are sub
Hi Tony --
This is a question better suited for the django-users mailing list;
django-developers is for discussion of developing Django itself, not
usage questions.
Thanks!
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
701 - 800 of 1372 matches
Mail list logo
