Hey folks --
MediaTemple, our hosting provider for djangoproject.com, is going to
be taking our server offline Thursday night while they give us more
RAM.
The window for downtime is some time between 9PM and 4AM, though the
actual downtime itself should be less than an hour.
Since most people us
On Tue, Jan 29, 2013 at 6:27 PM, Russell Keith-Magee
wrote:
> Of course, this is Mongolian Standard Time, correct?
Naturally :)
Bleh. PST. Sorry 'bout that!
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this
The only historically-accurate answer is: "because it seemed like a
good idea at the time."
Remember, this was 2008. So one problem was that Django's DB APIs
weren't very polished, so GeoDjango had to do a bunch of trickery.
Bringing it into core gave a good way towards pushing that flexibility
do
On Tue, Feb 12, 2013 at 10:21 AM, Val Neekman wrote:
> If I had to choose between GeoDjango and South as a core package, I'd go with
> South for sure.
FTR, that's in the works.
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To un
Hi folks --
I'm sitting here in a hotel room, after day 4 of a 5-day Django class
I'm teaching for a client. This is something I've been doing a fair
bit of over the last few years, and tonight I took the opportunity to
pull together some of my notes on what sorts of things people struggle
with as
On Mon, Feb 18, 2013 at 7:41 AM, Aymeric Augustin
wrote:
> The goal of my proposal is to save the cost (in response time) of establishing
> the database connection, in vanilla Django, without compromising reliability.
> I'm trying to help people who aren't even aware of the problem :)
>
> The impl
On Mon, Feb 18, 2013 at 1:51 PM, Michael wrote:
> I will argue, however, that the AWS use case is a reason we need this to be
> an OPTION, not automatic.
Check out Aymeric's patch; it is indeed an option triggered by
DATABASES[CONN_MAX_AGE].
Jacob
--
You received this message because you are s
releases-issued/.
Sorry about the mixup!
Jacob Kaplan-Moss
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.c
Would a dedicated Oracle build slave machine (VM, probably) help? If
so I can most likely provide one. Perhaps I could provide a host, Shai
could set it up to run Oracle, and Florian et al. could integrate it
into our existing Jenkins instance?
Jacob
On Mon, Feb 25, 2013 at 10:27 AM, Shai Berger
Hey Aymeric -
Yes, I think this is the right thing to do: +1.
Jacob
On Fri, Mar 1, 2013 at 4:48 AM, Aymeric Augustin
wrote:
> Hello,
>
> I'd like to improve transactions handling in Django. The first step is the
> current emulation of autocommit with database-level autocommit.
>
> ** Rationale
On Sat, Mar 2, 2013 at 3:27 PM, Shai Berger wrote:
>> I believe that the level of backwards-incompatibility described above is
>> within acceptable bounds for Django 1.6.
>
> I believe this is the core of our disagreement here.
I'm with Aymeric: the current behavior is bad enough, and this is a
b
On Fri, Mar 1, 2013 at 12:04 PM, Florian Apolloner
wrote:
> Doing it outside of Django core if fine, inside core is -0 to -1 from me.
I actually strongly disagree: I think Django *should* ship an
"authenticate-using-email" system. It's *SUCH* a common desire, and
it's actually fairly tricky to ge
Hm.
I'm +1 on cleaning up the names but do we *really* have to use a
metaclass for this? Seems to me this is "gratuitous use of a
metaclass" territory, especially given the shenanigans you have to go
through with subclassing the metaclass.
I'd be a lot happier with this patch if it just did t
On Wed, Mar 6, 2013 at 12:21 PM, charettes wrote:
> The use of the metaclass make sure you're not shooting yourself in the foot
> all and all the metaclass subclassing trouble should only concern a minority
> of users who most probably know what they're doing.
Ah, OK, that's the missing part I wa
To clarify a little bit, the reasons I think it's a good idea are because:
* It's simple and clean.
* It doesn't require another setting, nor new middleware methods, nor
new anything actually.
* It makes Django inter-op a tiny bit better (if you want to use
Django's ORM and request-linked commits
Hi folks --
This one's simple: I'd like to deprecate `django.contrib.comments`,
scheduling it to be removed in a couple of releases.
My rationale is this: if you don't really care much about how comments
work but just want something easy, then Disqus (and its competitors)
are easier to use and ha
On Mon, Feb 25, 2013 at 4:48 PM, Florian Apolloner
wrote:
> So all in all I think we could enable travis,
I agree, +1 from me.
> but I have two questions:
> * How much bash magic do we want in the .travis.yml file? One option would
> be to use a separate repo like I did in my initial work:
> ht
On Wed, Mar 6, 2013 at 3:22 AM, Marc Tamlyn wrote:
> I don't know why Oracle is included and MSSQL is not [...]
It's essentially because a group of people made a concerted effort to
get the Oracle backend up to snuff (around the 1.0 timeline, I think?)
and then committed to maintaining it. Lately
On Thu, Mar 7, 2013 at 5:55 PM, Russell Keith-Magee
wrote:
> However, I'd argue against using /dev/null as a disposal mechanism. I don't
> think the code should ever completely disappear. If someone offers to take
> over, that's great; but just because nobody volunteers to maintain the
> project,
On Sun, Mar 17, 2013 at 10:33 AM, Aymeric Augustin
wrote:
> Would anyone like to review it?
I would, and will probably have edits, but +1 on committing now. This
looks good enough to add right now, we can iterate a bit after it's
in.
Jacob
--
You received this message because you are subscribe
Hello fellow Djangonauts,
We have difficult news: Malcolm Tredinnick has passed away.
Malcolm was a long-time contributor to Django, a model community member,
a brilliant mind, and a friend. His contributions to Django — and to
many other open source projects — are nearly impossible to enumerate.
Hi Omer -
OK, I think it's time for you to drop this. Thanks for your
suggestions, but we're not going to be adding this to Django.
Jacob
On Sun, Mar 24, 2013 at 9:32 AM, Omer Katz wrote:
> 2013/3/24 Russell Keith-Magee
>>
>>
>> On Sun, Mar 24, 2013 at 6:28 PM, Omer Katz wrote:
>>>
>>> You ar
On Mon, Mar 25, 2013 at 10:50 PM, meric wrote:
> What action, if any, do you suggest I take now?
If it's gonna get in, you/we need to talk Adrian into dropping his -1 vote.
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubsc
Adrian's one of the BDFLs (I'm the other), so if he says "no" that stands.
Usually, we operate the way most open source projects do: "rough
consensus and working code". You've got the second ("working code") so
you need to work on the first, I think. Usually a strong consensus is
enough to overrid
See https://docs.djangoproject.com/en/dev/internals/git/#other-branches
and also
https://docs.djangoproject.com/en/dev/internals/release-process/#bug-fix-releases
The short version is that stable/* branches only receive "critical"
backports: security fixes, crashers/data-loss bugs, and occasional
On Thu, Mar 28, 2013 at 2:46 PM, Yo-Yo Ma wrote:
> Will bugs like that one I mentioned in the OP actually be eventually fixed
> in 1.5.1, instead?
No, it's not a critical fix, so the fix'll be in 1.6.
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django d
Hi folks --
We've just released Django 1.5.1, a bug fix release that cleans up a
couple issues with last month's 1.5 release.
The biggest fix is for a memory leak introduced in Django 1.5. Under
certain circumstances, repeated iteration over querysets could leak
memory - sometimes quite a bit of
On Tue, Apr 2, 2013 at 4:49 AM, David Danier wrote:
> This is somethign that does not need to be inside Django core. So why
> not just start an thirt party app implementing the proposal?
I did just that: https://pypi.python.org/pypi/django-multiurl.
Turns out it takes a fair bit of spelunking in
al docs.
>
> Felipe 'chronos' Prenholato.
> Linux User nº 405489
> Home page: http://devwithpassion.com | http://chronosbox.org/blog
> GitHub: http://github.com/chronossc/ | Twitter: http://twitter.com/chronossc
>
>
> 2013/4/2 Jacob Kaplan-Moss
>>
>> On Tue
On Tue, Apr 2, 2013 at 11:02 PM, Russell Keith-Magee
wrote:
> In short, no - Twitter isn't a particularly reliable source for updates.
> Someone in the core team will usually tweet about the release, but since
> it's hard to share logins to a single Twitter account, and the person who
> owns Djang
On Wed, Apr 3, 2013 at 10:19 PM, Kevin Veroneau wrote:
> Is this Epydoc error related to Epydoc or something that Django shouldn't
> have done in it's source code?
It looks perhaps like something you'd need to fix -- the message about
settings.configure() indicates that you're loading code that r
Hi folks --
"Design decision needed" is where good tickets go to die. The idea was
that someone could come by later and make the decision, but as it
turns out, Someone doesn't work here. In practice, DDN tickets sat
open, often for years, and just frustrated everyone.
So we're getting rid of DDN;
On Fri, Apr 12, 2013 at 8:54 AM, Gustavo Narea
wrote:
> So I guess that means that it won't be considered for inclusion in Django?
> If so, I'll close that ticket.
Hm, I wouldn't be so hasty -- it's something I, at least, would like to include.
Of course, the concerns about the implementation ar
Hi Ashwin -
On Tue, Apr 16, 2013 at 2:10 PM, Ashwin Kumar wrote:
> is there any way to implement websockets in django?
> if not, any other packages to combine with django.
There are quite a few third-party apps and demos out there, so many
I've lost track. I recommending searching GitHub.
> i
Hi Christopher -
Thanks for the proposal, this is quite good. I really appreciate the
detail; it's clear you've put a lot of thought into this. In general,
I think this is a strong proposal and one I'd support. However, I do
have some comments/feedback:
1. We've had some discussions about bringin
On Wed, Apr 17, 2013 at 10:50 AM, Emil Stenström wrote:
> {% extends "base.html" %}
> {% block content %}
> Be careful when changing these settings!
> {% block content %}{% endblock %}
> {% endblock %}
I find this intensely confusing -- I can't build a mental model of
what's going to be r
On Thu, Apr 18, 2013 at 6:42 PM, Russell Keith-Magee
wrote:
> So - the secret to getting into the GSoC isn't the project title you pick -
> it's the quality of your proposal.
This. A thousand times this.
I think there's a perception among people applying to GSOC that we're
judging the project. T
Hi Carsten -
On Fri, Apr 19, 2013 at 10:43 AM, Carsten Fuchs wrote:
> sorry to bother you here, but I posted to django-users first
> (https://groups.google.com/d/msg/django-users/WHnCxHkEVjE/9puR4youvwsJ) and
> there was no reply, so please let me re-try here:
Unfortunately, we can't help you. D
On Fri, Apr 26, 2013 at 3:54 AM, Christopher Medrela
wrote:
> 1. First of all, I noticed that the license of django-secure is copyright.
> Google forces us to release code under one of approved license [1], so a
> question to Carl Meyer: do you mind changing license?
django-secure is licensed und
On Mon, Apr 29, 2013 at 6:25 AM, Christopher Medrela
wrote:
> Jacob, as you said, I deleted django-updates part, but I ended with a
> proposal taking only 9 weeks. Did you mean also scheduling more than 6 weeks
> for the first part of the proposal (writing the new framework) and
> "stretching" the
Hi folks -
Unless there are strong objections, here's what I'm thinking for the
Django 1.6 release timeline:
Alpha: May 16
Beta: June 20
RC: Aug 1
Final: as early as Aug 8, or later if more RCs are needed.
Remember that Alpha is the deadline for "big" features, so if you've
got something sizable
On Wed, May 1, 2013 at 7:38 AM, Satinderpal Singh
wrote:
> I wish to be a part of GSoC, and i have a plan to improve some
> features of forms of the Django, like adding different formats such as
> tables with different layouts. Also some improvements in the default
> form settings in the Django, l
Hi Satinderpal -
Thanks for your effort! Unfortunately, I think you've still got a long
way to go.
Your proposal is fundamentally quite vague. You seem to understand
some of the problems with the current forms API, but I really can't
tell exactly what you plan to do about it. The actual meat of y
On Thu, May 2, 2013 at 4:42 AM, Aymeric Augustin
wrote:
> Shouldn't we push the alpha to May 23rd, all the more since we plan to fork
> the stable/1.6.x branch at the beta?
That sounds reasonable; give us a chance to get any work done at
DjangoCon Europe into the tree before we roll the alpha.
S
On Thu, May 2, 2013 at 1:34 PM, Michał Nowotka wrote:
> http://www.techempower.com/benchmarks/#section=data-r4 django performance is
> really bad comparing to other popular web frameworks. Are there any plans to
> change this situation?
First, there are some very serious problems with those "benc
While I share some of Andrew's concerns, I do think this is still a
fairly good topic for GSoC.
However, I think the only way it could happen would be if Nate wants
to mentor the project; Nate, can you mentor? If so, you should hook up
with Andrew and make sure you apply to be a mentor so we can h
On Wed, May 8, 2013 at 2:00 PM, Carl Meyer wrote:
> Jacob has suggested that back-compat breaks in test-running are not as
> serious as in production code, and that we should just switch to the new
> test runner by default in Django 1.6.
I still think this. I don't see the need to maintain compat
On Sat, May 11, 2013 at 6:36 PM, Anssi Kääriäinen
wrote:
> Does the proposal look acceptable?
Yes. +1 from me.
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send a
Hi Tom --
It really sucks that when I say "if you have feedback please send it
over here", you hear "I'm not listening".
I'm sorry, but I don't have the mental bandwidth to follow 20,000
individual tickets. It's impossible. I just fucking can't do it.
Believe me, I've tried, and failed, many time
On Mon, May 13, 2013 at 2:12 AM, Chris Wilson wrote:
> The status WONTFIX sounds awfully rude to me.
I've thought so, too, but every time I've tried to come up with an
alternate name I've failed. Any suggestions?
FWIW, "won't fix" has a long history as a term of art in bug tracking;
it refers to
On Mon, May 13, 2013 at 9:56 AM, Tom Evans wrote:
> I don't think anyone is asking you to do this. This ticket in question
> wasn't lacking bandwidth from committers, it was visited many times by
> committers, who each time summarily dismissed the ticket - "We're not
> doing this because x years a
FYI - djangoproject.com is currently down, I'm investigating and I'll
try to have it back up ASAP.
In the meantime, if you need to get to the docs, you can hit up the
ReadTheDocs mirror: http://django.rtfd.org/
Thanks for your patience,
Jacob
--
You received this message because you are subscr
silient against any future outages like this.
Thanks for your patience!
Jacob
On Tue, May 14, 2013 at 5:53 PM, Jacob Kaplan-Moss wrote:
> FYI - djangoproject.com is currently down, I'm investigating and I'll
> try to have it back up ASAP.
>
> In the meantime, if you need t
As suggested to me (privately) by Tom Evans, I've started trying to
keep an eye on tickets that bounce back and forth between open and
wontfix. If a ticket "bounces" a few times it's probably a sign that
there's something going on, and we may want to proactively start a
mailing list thread rather t
On Tue, May 14, 2013 at 5:41 PM, Cal Leeming [Simplicity Media Ltd]
wrote:
> * Make the 5-for-1 (or 10-for-1) system official, not many people seem to
> realise this exists. This will give incentive to core devs to spend a bit
> longer on a ticket, maybe even throwing in a pleasentry or two (optio
Hi folks --
Does anyone have some clever thoughts on how to solve #16650?
https://code.djangoproject.com/ticket/16550#comment:7 is a good
summary of the problem: if you're using extensions, you need a way to
run some custom SQL in tests after the DB gets created by the test
harness but before syn
Hi folks -
tldr: there's a new DEP 1
(https://github.com/django/deps/blob/master/final/0001-dep-process.rst),
read it if you think you might want to submit a DEP. The biggest change is
a clear articulation of exactly how the process works. Read on for
background and more details.
About six mo
Hi folks --
A bit of context before I dive in: at DjangoCon, Eric Florenzano gave
a "what's broken about Django" talk. I sadly had to miss DjangoCon,
and so I'm anxiously waiting to see the video, but I did see one thing
in the slides I thought I should address right away. Actually, this is
someth
Hi folks --
Over the course of this week I'm going to be upgrading and improving
the djangoproject.com infrastructure. We'll get some Trac upgrade
action (thanks to Jeremy Dunck, Jannis, and a few others), a better
/community page (thanks to Justin Lilly), and I'll be setting the
stage for a sysad
Hi --
On Thu, Sep 23, 2010 at 1:38 PM, Yo-Yo Ma wrote:
> I think I've found a bug in auth.login.
Thanks for the report.
However, for this to be useful, we're going to need a *lot* more
information -- a complete traceback, the code you used to trigger the
error, etc. Quoting from the contributio
On Thu, Sep 23, 2010 at 2:18 PM, Yo-Yo Ma wrote:
> Hey Jacob, understood. Here's some more details that might help:
[snip]
> if user.check_password(request.POST.get('password',
> '')):
> login(request, user)
As Santiago mentioned, you need to call authenticate()
On Thu, Sep 23, 2010 at 3:33 PM, Yo-Yo Ma wrote:
> I'm simply proposing the idea of having the development server
> explicitly set something to indicate a "in development" status, so
> that if that does not exist you can make the assumption that the
> project is live.
This is exactly what the set
On Fri, Sep 24, 2010 at 3:50 PM, Yo-Yo Ma wrote:
>
> What if I want dev settings in version control?
>
> What if I want "explicit"?
At this point this discussion is getting pretty far off-topic; can you
please take it to django-users?
Thanks,
Jacob
--
You received this message because you are
Hi folks --
Starting today, we're going to be making some minor but significant changes
to the way the Django core committer team "does business."
Put simply, we're changing the way we make decisions so that we can make
important policy and design calls more quickly and easily. In a nutshell:
*
On Wed, Sep 29, 2010 at 1:34 PM, dartdog wrote:
> So maybe subdividing the areas of responsibility might help? I know it
> is generally recognized that certain comitters have specific expertise
> but it might make it easier to shore up some of the bus areas like the
> orm as well if the teams are
On Wed, Sep 29, 2010 at 3:21 PM, subs...@gmail.com wrote:
> Speaking of which... who is interested in admin these days? Been
> trying to scare up some feedback @ http://code.djangoproject.com/ticket/5833
> for some time now.
Please don't derail threads with unrelated topics like this. It makes
di
On Thu, Sep 30, 2010 at 8:56 AM, Russell Keith-Magee
wrote:
> If you have any objections, now is the time to raise them.
This isn't an objection, per se -- don't let it stop you committing --
but I'm somewhat concerned with the verbosity of the LOGGING setting.
We're adding 40 lines of configurat
On Thu, Sep 30, 2010 at 11:34 AM, Yo-Yo Ma wrote:
> I would
> propose putting an aggregation function list on that page, rather than
> letting the user eventually find the list at the bottom of the
> QuerySet page. Or, put a prominent link near the top that suggests
> visiting QuerySet docs for a
On Fri, Oct 1, 2010 at 1:44 AM, Tai Lee wrote:
> I'd like to suggest (1) easy to find and use pre-defined searches to
> find tickets at each stage of triage, (2) a clearer indication of the
> next steps and the person responsible for it whenever a ticket is
> reviewed, and (3) tickets that have be
On Fri, Oct 1, 2010 at 4:46 PM, Ivan Sagalaev
wrote:
> During a sprint before 1.2 I was proposing to commit my ticket [9886] that
> deals with adding a .read() method to HttpRequest. Adrian suggested that it
> was too late then and it's better to bring it up during 1.3 cycle. So here
> it is.
Loo
On Mon, Oct 4, 2010 at 12:08 PM, Alex Gaynor wrote:
> Given that the primary complain against the __new__ solution is that
> it's unintuitive to Python programmers that instantiating their class
> results in some other class, why not simply go with a more explicit
> classmethod. Simply used as:
>
On Tue, Oct 5, 2010 at 8:03 AM, Russell Keith-Magee
wrote:
> Ok - so to kick the process into the next phase, I've just created a
> Django branch in my bitbucket repo [1] to cover introducing this to
> trunk.
I gave this a quick review and nothing huge jumped out. Looks good so far.
One point of
On Wed, Oct 6, 2010 at 10:30 PM, Russell Keith-Magee
wrote:
> Strictly, it needs to be put on a deprecation path [...]
You know, I really don't think this is a big enough deal to bother
being completely picky about the deprecation policy here. It's a silly
setting that should have been removed pr
Hi folks --
Google's open source team is putting together a new program, called
"Google Code-in". It's a program to get 13-18 years old students
involved in open source by giving them sets of small, distinct tasks
to work on. They did a similar program last year, called GHOP; Django
didn't partici
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 shortly and I'm planning on
sending an email out to the whole backlog
On Mon, Oct 11, 2010 at 12:29 PM, Alex Gaynor wrote:
> I've uploaded a new patch [...]
Looks pretty good to me.
I must say, though, that I'm not completely happy with the API. I find
``assertNumQueries(number, callable)`` a bit non-obvious. The context
manager helps quite a bit, but I'd really p
On Tue, Oct 12, 2010 at 9:32 PM, Russell Keith-Magee
wrote:
> There are a bunch of modifications that we want to make to
> docs.djangoproject.com, and providing support for other languages is
> part of those improvements. Some recent additions to Sphinx should
> make it much easier to manage this
2010/10/18 Łukasz Rekucki :
> Somehow related, I was wondering today, would it be a good idea to try
> to rewrite contrib.auth views in terms of CBV, so that other parts of
> Django could benefit.
I'm not particularly clear on what other parts would benefit -- fill me in?
In general, I frown on r
On Tue, Oct 19, 2010 at 12:24 PM, David Gouldin wrote:
> Thoughts/opinions?
Looks like a good idea to me. I've certainly used ssi as a hack for
this before, so getting a noparse/verbatim tag into Django sounds
great.
Jacob
--
You received this message because you are subscribed to the Google G
On Tue, Oct 19, 2010 at 4:31 PM, James Bennett wrote:
> If we're going to do this, could we also look at deprecating the
> 'templatetag' template tag? There are a couple cases a 'verbatim' tag
> wouldn't cover that 'templatetag' wouldn't, but I'm kinda hard-pressed
> to think of when they'd ever c
On Wed, Oct 20, 2010 at 1:48 PM, Mikhail Korobov wrote:
> So please add the 'render' shortcut in 1.3.
It's one of the things on my list. If you'd like to make it happen
faster, a patch + tests would make it a no-brainer for me.
Jacob
--
You received this message because you are subscribed to t
2010/10/20 Mikhail Korobov :
> There is an unresolved question in the ticket: "The only hesitation is
> the relationship with #12815; we should resolve that decision before
> committing anything for this ticket."
>
> #12815 is about introducing TemplateResponse. Is the patch with
> 'render' shortcu
On Wed, Oct 20, 2010 at 3:04 PM, Waldemar Kornewald
wrote:
> I wish that were the case. The staticfiles documentation says:
>
> """
> Remember to run :djadmin:`collectstatic` when your media changes;
> the view only serves static files that have been collected.
> """
I actually wrote that without
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 patch was updated numerous times
> on the ticket [1] this month, but was there an associated review on the
> mailing l
On Thu, Oct 21, 2010 at 3:50 AM, Waldemar Kornewald
wrote:
> With this reasoning we could as well add django-debug-toolbar, South,
> django-registration and many other popular apps. What makes
> staticfiles different? Seriously, I don't see it.
Jannis proposed that we add static files in. Brian c
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 proposal.
Well, that's why we use revision control: if there's a rough consensus
that a commit was a m
On Thu, Oct 21, 2010 at 1:25 PM, Waldemar Kornewald
wrote:
> Thanks a lot for the clarification. So, then the "bad batteries" part
> in Eric's talk "Why Django sucks and how we can fix it" doesn't
> receive much agreement within the Django core team?
I think that's kind of irrelevant: people comp
On Thu, Oct 21, 2010 at 2:33 PM, Tobias McNulty wrote:
> What's the argument against serving the original files directly?
It means that when you add new apps you have to update your
Apache/Nginx/whatever config. Back in the day (pre-open-source), every
time you added an app you had to edit your A
On Fri, Oct 22, 2010 at 11:21 AM, Silvio wrote:
> I opened ticket #13717, and it seems to be reproducible by other
> people. Someone contributed a patch, but the ticket is "stuck" because
> it needs tests.
>
> I would really like to see this fixed by 1.3, so I'd be more than
> happy to write these
On Fri, Oct 22, 2010 at 5:59 PM, Christophe Pettus wrote:
> Why does transaction management only commit on is_dirty?
It's a bug: http://code.djangoproject.com/ticket/9964.
Looks like the patch there is OK, but still needs some work (there's a
couple of TODOs still).
Jacob
--
You received this
On Wed, Oct 27, 2010 at 4:32 PM, Adrian Holovaty wrote:
> I'm inclined to say we do the former -- restore the "ne" lookup type
> -- because it's a quick fix, and ask somebody to write up a patch for
> the latter. Does anybody have strong opinions against this? If not, I
> can restore the "ne" look
Hi Waldemar --
Like a few in this thread, I'm really having trouble understanding
exactly what you're proposing. I think the best thing, then, would be
if you could write some code to do whatever it is you'd like.
Just a proof-of-concept is totally fine -- I don't mean to ask you to
invest a lot
On Fri, Oct 29, 2010 at 11:26 AM, Waldemar Kornewald
wrote:
> (see attachment which "implements" method (2) :).
OK.
For the record, I really don't want to be a dick here, but I think
what follows comes across that way. I'm quite sorry for not being able
to communicate myself in a less jerk-y way
On Mon, Nov 1, 2010 at 4:13 PM, Paul Oswald wrote:
> Some of the issues in that list seem like they would be small patches. Would
> it be possible to have someone mark the low hanging fruit as 1.3?
Yes - go ahead and do it!
We usually spend the last couple-three weeks of each release cycle
push
On Mon, Nov 1, 2010 at 4:31 PM, Tom X. Tobin wrote:
> I've updated the changes for ticket #12248 and placed them on GitHub:
>
> http://code.djangoproject.com/ticket/12248
>
> http://github.com/tomxtobin/django/tree/template-import-refactor-t12248
>
> Is there any chance this might make it into the
On Wed, Nov 10, 2010 at 1:39 PM, Stephen Kelly wrote:
> Can someone confirm that the email I sent yesterday made it through? Last
> time I emailed that list it was marked as spam apparently.
Yes, we've got it. We'll get back to you shortly - sorry for the delay.
Jacob
--
You received this mess
On Thu, Nov 11, 2010 at 4:39 PM, Stephen Kelly wrote:
> I have a patch to allow localizing localizable values like {{ _(foo) }},
> which I think is more convenient. It sort of mixes up the meaning of _() to
> be both for translatable strings and localizable dates and numbers, so I
> thought I'd as
On Sun, Nov 21, 2010 at 8:55 AM, hutch_burgopak wrote:
> This is probably a dumb question, but what is the policy on this?
We don't have a specific plan or timeline in mind. Like everything
else in open source, it'll get done when enough people are willing to
devote enough time (or money) to the
On Wed, Nov 24, 2010 at 12:31 PM, Paul McLanahan wrote:
> I created ticket #14770 (http://code.djangoproject.com/ticket/14770)
> because I ran into a situation this week where I only had access to
> the request, but needed to set a cookie. As the ticket says, I did
> solve this problem with a midd
On Wed, Nov 24, 2010 at 1:50 PM, Paul McLanahan wrote:
> There are just situations where you need to have the ability to cause
> a cookie to be set, but can't yet create the response object.
Okay, but you've said this twice without giving any examples. Which
makes it very easy for me to argue tha
601 - 700 of 1372 matches
Mail list logo
