Another approach would be to do what I laid out in this talk at DjangoCon US
2015, following the last Summer of Code student who tackled (tangentially) this
problem.
https://www.youtube.com/watch?v=VgM0qmpHDiE
That is - finish the modifications needed to Django’s core such that an
arbitrary m
Hi Tom,
My immediate reaction is No, for three reasons:
1. My experience has been that Cython isn’t especially stable. Admittedly, I
haven’t looked at it for a couple of years, but when I did, I ended up getting
caught in some really nasty bugs that came back and forth between micro
versions.
On Tue, Mar 21, 2017 at 2:37 PM, Adam Johnson wrote:
> It does seem like a somewhat arbitrary historical restriction. Collin's
> PoC change is surprisingly small and simple.
>
> Seems like it would be fine if Django allowed add() and let any errors
>> about missing data bubble-up.
>>
>
As the per
Hi Mark,
On Thu, May 5, 2016 at 8:41 AM, Mark Lavin wrote:
> Major features have never been perfect, no, but they have in the past
> typically gone through two paths to prove out their design/API/usefulness.
> One is as an established and mature third-party app such as messages,
> staticfiles, a
Hi Geoffrey
On Tue, May 3, 2016 at 3:42 AM, Geoffrey Martin-Noble wrote:
> Is there a particular reason Django doesn't implement table locks? These
> are vendor-specific, but seem to be common to various SQL backends, which
> is something Django generally does well.
>
I’m not aware of any philo
On Thu, Mar 24, 2016 at 6:36 AM, Florian Apolloner
wrote:
> Sorry, but this is no proposal -- this is a bad joke. You will need to put
> way more work into
>
Florian - While this is true, this is an excessively harsh way of
delivering the news. We have no reason to believe that Girish is activel
Hi Chitra,
Django’s contribution guide is here:
https://docs.djangoproject.com/en/1.9/internals/contributing/
That gives you a step-by-step guide to the ways you can contribute, and how
to get started.
If you want some more specific guidelines or mentoring, you’ll need to tell
us a bit more abo
It would also be worthwhile looking into the prior art on this topic. We
had a GSoC project for non-relational data stores a few years back, and
came to the conclusion that it probably wasn’t viable. You can dig into the
archives to find out why.
If you’re interested in adding non-relational suppo
Hi Becka,
On Thu, Mar 3, 2016 at 8:55 AM, Becka wrote:
> Hi,
>
> I've been spending some time looking over the docs, and I'm really
> interested in making them more approachable to relative n00bs like myself,
> particularly when it comes to contributing to Django and the docs.
>
Fantastic! This
On Wed, Feb 10, 2016 at 7:25 AM, Tim Graham wrote:
> The introduction to the admin in the docs [0] reads:
>
> "One of the most powerful parts of Django is the automatic admin
>> interface. It reads metadata in your model to provide a powerful and
>> production-ready interface that content produce
Weighing in on Jira specifically - I’ve had to use it on a number of
projects, and I’ve never had a good experience with it. That might be
because the Jira instances were badly configured - bit if that’s the case,
it suggests to me that there’s a deeper problem with Jira being too complex
for it’s
On Sun, Dec 27, 2015 at 11:00 PM, Wim Feijen wrote:
> By default, when you create a formset from a model, the formset will use a
> queryset that includes all objects in the model (e.g.,
> Author.objects.all()).
>
> In most use cases, people will want to use a specific subset of data and
> will co
On Thu, Dec 10, 2015 at 7:52 PM, Alexandru Damian wrote:
> Hi Russ,
>
> Thanks for coming back to me so quickly.
>
> On Thursday, December 10, 2015 at 12:30:03 AM UTC, Russell Keith-Magee
> wrote:
>>
>> HI Alex,
>>
>> On Wed, Dec 9, 2015 at 9:57
HI Alex,
On Wed, Dec 9, 2015 at 9:57 PM, Alexandru Damian wrote:
> Hi,
>
> I've compiled the django.template.{base,context,context_processor} modules
> with cython in order to speed up template rendering.
>
> I've come to the conclusion that this is needed after profiling long page
> loads that
Hi Asif,
On Wed, Nov 4, 2015 at 12:17 AM, Asif Saifuddin wrote:
> I would like to create an experiemental repo on my github for
> experiementing the sqla support to django orm, hence some useful resource
> indicator would be great. sqla have core engine and orm on top of it, so
> the idea way to
Hi Tim,
On Wed, Oct 28, 2015 at 12:50 AM, Tim Graham wrote:
> In 2014 I started to research if we could offer a Google Summer of Code
> project aimed at improving Django's process for collecting and organizing
> CLAs. I didn't complete that proposal when I found some existing solutions,
> in par
+1. Sounds like a great idea to me.
Russ %-)
On Tue, Oct 27, 2015 at 1:22 AM, Tim Graham wrote:
> On Trac [1], Alex says, "Django did a tremendous service to its users by
> making strong password hashing be the default. The world is pushing
> forward, and now 2fa is the next standard that many
Agreed. This didn’t really affect 1.4 because 2.7 was in a very stable
place, and we didn’t support Python 3. Now that we’re Py3 focussed, and
Python has a similar backwards compatibility policy to Django (i.e., Python
3.7 isn’t going to break all Python 3.6 code in subtle ways), it makes
sense tha
On Sat, Oct 24, 2015 at 5:42 AM, Marc Tamlyn wrote:
> I disagree with this system check and I would like to see it reverted
> before 1.9 final.
>
I agree - I’d argue that this check is demonstrably *incorrect*.
> I admit that my opinions here are skewed by the fact that I think model
> level v
Hi Yash,
The Google Summer of Code 2016 hasn’t even been announced yet. Django
hasn’t applied to be a mentor organization, and it’s not yet certain that
we’ll even apply.
However, assuming that we do - the best thing you can do to improve your
chances to be accepted as a Django GSoC student is to
On Wed, Sep 23, 2015 at 12:54 AM, Tim Graham wrote:
> The second patch has been committed, and the first one is still under
> review.
>
> Florian says "with all that forth and back [on the pull request] I am not
> sure if it is not better to defer it to 1.10, i.e. I completely missed the
> base64
On Wed, Sep 23, 2015 at 7:06 AM, Josh Smeaton wrote:
>> Could we have permanent backward-compatible (no deprecation timeline)
>> shims? I'm -0 if not because it's yet-another thing that everyone needs to
>> change when upgrading.
>>
> +1
That would be my preferred approach, too.
Yours,
Russ Mage
Hi Asif,
It depends entirely what you mean by "support".
Django is just Python, so there's absolutely no reason you can't write
a Django site that uses Django for the URLs, views and forms, but
SQLAlchemy for the data access.
Out of the box, you won't be able to use ModelForms or the Admin.
Howe
On Wed, Sep 2, 2015 at 10:29 PM, Tim Graham wrote:
> Russ tried to complete the "EmailUser" solution for 1.7, but if I remember
> correctly, there was some issue with testing that couldn't be easily
> resolved.
>
> https://github.com/django/django/compare/master...freakboy3742:emailauth
The issue
Hi Tim, Meet
I know this is very late to be mentioning, but one idea that worth
raising: DjangoCon US is next week (in Austin). Thursday and Friday
are coding sprints, where there will be many people (including a good
chunk of the core team) looking for projects to hack on.
Microsoft is already a
Hi Meet,
The Fellowship committee has just approved this, so go ahead and plan
whatever you need to plan.
Yours,
Russ Magee %-)
On Sat, Aug 29, 2015 at 6:21 AM, Meet Bhagdev wrote:
> Thanks Russ!
>
> On Tuesday, August 25, 2015 at 6:34:54 PM UTC-7, Russell Keith-Magee wrote:
>&g
On Sat, Aug 22, 2015 at 8:28 PM, Tim Graham wrote:
> I agree it would be great to get some help running the Django tests on
> Windows. I run them in a local virtual machine every so often, but I would
> love to be able to delegate fixing Windows issues. Meet, can your team
> provide ongoing help
On Fri, Aug 21, 2015 at 7:35 AM, Tim Graham wrote:
> In my experience the "easy pickings" flag is ill-defined and insufficient
> for describing the difficulty of a ticket. I don't want to get stuck in
> categorizing tickets just for the sake of it, but I think a drop down with
> options like the
On Fri, Aug 7, 2015 at 3:06 PM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> > On 7 août 2015, at 05:43, Curtis Maloney
> wrote:
> >
> > I'd probably go with updating the documentation to say they're legacy
> > tags, you're better off using {% if %} now, and warn they may be
>
Hi Mudassar,
If you're looking for help on how to use or deploy Django, you should post
to the django-users mailing list. This list is for discussing the
development of Django itself.
Yours,
Russ Magee %-)
On Tue, Aug 4, 2015 at 7:36 AM, Mudassar Hashmi <
mudassarziahash...@hotmail.com> wrote:
On Thu, Jul 23, 2015 at 12:40 AM, Tim Graham wrote:
> Lately we've had some packaging problems due to mistakes in MANIFEST.in,
> mostly due to missing files in the source distribution because we forgot to
> update MANIFEST.in for new or moved files. Currently it looks like this:
>
> include READM
On Mon, Jul 13, 2015 at 11:00 PM, Donald Stufft wrote:
> I’m fine with this, but just be warned that it does mean anything
> that ships a Django app will need a zip_unsafe=True or else they
> no longer support being installed with easy_install.
... and I'm sure both the people who still use eas
Hi James,
I'm inclined to agree - the fact that Django added a new field type in 1.8,
but can't serialize that type should be considered a bug, not a new feature.
If there's no objection on this thread, then the ticket should be
re-opened, and a pull request for the backport submitted.
Yours,
Ru
day, June 28, 2015 at 7:51:22 PM UTC-4, Russell Keith-Magee wrote:
>
>>
>> On Mon, Jun 29, 2015 at 7:32 AM, Josh Smeaton
>> wrote:
>>
>>> I'm not quite up to date on XML in databases (I've never had to use XML
>>> in a database), but don'
On Mon, Jun 29, 2015 at 7:32 AM, Josh Smeaton
wrote:
> I'm not quite up to date on XML in databases (I've never had to use XML in
> a database), but don't the majority of core backends support XML in some
> way? If so, I'd probably like to see an attempt to build out XML support
> such that all/m
On Thu, Jun 4, 2015 at 4:19 PM, Tim Graham wrote:
> I think we should keep Trac focused on tracking bugs. The dsf-members
> mailing list seems like a natural place to raise these ideas, although
> that's a more limited audience, so I'd feel free to raise them here unless
> someone else can sugges
I'm completely on-board with the idea of switching to a "real" web server
rather than continuously improving our own.
However, there might be better options than gunicorn. Graham Dumpleton has
released mod_wsgi-express:
http://blog.dscpl.com.au/2015/04/introducing-modwsgi-express.html
which is a
Hi Anoop,
I agree with Tim and Markus' comments - you're proposing to implement
a specific behavior where there is no "clearly right" answer. This
strikes me as something that is entirely site-dependent logic. You
don't even need a custom user model - a template tag (or even a
filter) could do thi
On Sat, Apr 4, 2015 at 12:24 AM, Loek van Gent wrote:
> Hi all,
>
> Is anyone using DKIM signing for densing emails? Does it make sense to you
> to have a feature like that in Django core or is this typically something
> that should be in it's own app?
> We use it to sign our emails so the don't
On Mon, Mar 30, 2015 at 1:36 AM, Pkl wrote:
> Hello all,
>
> I've noticed that all sql* commands that were in django core management
> have disappeared from the latest sources.
>
> However, even though Django now has builtin south-style migrations now,
> these *sql** commands (especially sql-all)
Hi Paulo,
On Sat, Mar 28, 2015 at 8:12 AM, Paulo Maciel
wrote:
> I started working with formset and found half cast, for example, when
> configuring a formset with min_num = 1, django requires that the first form
> of the formset (form-0) is completed, I see this as a bug, it should check
> for
Hi Alex,
On Thu, Mar 26, 2015 at 7:03 AM, Alexander Patel <
alexanderpa...@college.harvard.edu> wrote:
> Hello, all,
> My name is Alex Patel, and I am an undegraduate at Harvard College in the
> United States studying mathematics and philosophy. I intend to submit a
> proposal to work on Django's
Hi Varun,
I've just taken a look at this proposal; I've got some concerns.
* You say you can get test coverage from 81% to 90% - that's an admirable
goal, but is there any reason to believe that it is achievable? In many
cases, the coverage is low because a feature/branch is so difficult to test
I agree with Tim's assessment - this is not a compelling proposal at the
moment.
There is value in converting *some* of the function based views to CBVs,
but unilaterally converting all of them doesn't seem especially worthwhile.
The key thing is to identify what features need to be factored out.
Hi Zafack Billy,
Welcome! If you're interested in being a GSoC student with Django, you
should read our wiki page on the program.
https://code.djangoproject.com/wiki/SummerOfCode2015
>From there, you need to pick a project, and prepare a proposal describing
what you expect to achieve over the 12
Hi Mesut,
It wasn't clear that you were asking a question.
Django's GSoC wiki page contains details of what you need to do in order to
be a GSoC student for the Django project; the next step from your
perspective is for you to do some research on the projects that interest
you and write a proposa
On Sun, Mar 22, 2015 at 4:12 PM, Mesut Gülecen
wrote:
> Hi, my name is Mesut Gülecen, currently in second year of engineering
> at Canakkale Onsekiz Mart University in Turkey.
> I want to contribute to the development of Django. I have working upon
> Django already and I want to learning somet
that there is 12 weeks
worth of work here - the problem is that you need to convince us that *you*
know where those 12 weeks of work are.
Yours
Russ Magee %-)
On Sun, Mar 22, 2015 at 8:32 PM, Yichun Duan wrote:
> Thanks. Updated. :)
>
> 在 2015年3月18日星期三 UTC+8上午6:39:46，Russell Keith-M
On Wed, Mar 18, 2015 at 5:38 AM, Curtis Maloney
wrote:
> I found when taking the CBGV session in MelbDjango School, it was best to
> approach teaching CBV as an exercise in Interfaces.
>
> Once the students were familiar with writing basic views, and the patterns
> therein, much of CBGV became "o
Hi Yichun Duan,
Thanks for submitting a proposal - what you've submitted is a good start,
but it needs some more detail and clarification.
4.1: You say you're going to save the database-specific tests "to another
place" - Can you give specifics, or at least an idea of you current
thinking? How wi
Hi Mitchel,
Thanks for submitting a proposal (and for starting the process earlier than
2 days before the deadline). You get extra credit for being ambitious and
proposing something that isn't on the suggested projects list :-)
I have three concerns about this project:
Firstly, what's the curren
Hi Benjamin,
A few more details to whet your appetite (because this is a thing I've been
*thinking* about, but don't have anything to show)
The biggest sticking point at the moment is getting Python on the client
side. I'm aware of many attempts:
* Brython (http://www.brython.info) is an in-bro
Hi Yichun,
On Mon, Mar 9, 2015 at 4:13 PM, Yichun Duan wrote:
> Hi,
>
> I'm Yichun and I'm interested in the Project ' Improving the less popular
> database backends' in GSOC 2015. I major in computer science in Peking
> University. I've worked with C++, Java, Python and I've written several
> w
Hi Abhishek,
On Sun, Mar 1, 2015 at 1:16 PM, Abhishek Kumar wrote:
> Hi,
>
> I am Abhishek and am interested in the project titled "SQLAlchemy / NoSQL
> integration". I am good at data-structures and algorithms and have worked
> with C,C++, PHP, Python,C#, Javascript and Mysql. I have an interns
Hi Gavin,
I've lost track of how many times I've written that exact code when setting
up a new box - I just didn't wrap it up as a management command. There's a
similar testing cycle with new cache settings.
My only concern would be the one that Tim expressed - that it's ultimately
a one line she
On Wed, Feb 25, 2015 at 10:39 AM, Loïc Bistuer
wrote:
> >
> > On Feb 25, 2015, at 09:07, Russell Keith-Magee
> wrote:
> >
> > I have an operating system with a graphical user interface. The
> developers of that operating system spent an immense amount of time
On Tue, Feb 24, 2015 at 11:59 PM, Riccardo Magliocchetti <
riccardo.magliocche...@gmail.com> wrote:
> Il 24/02/2015 16:18, Florian Apolloner ha scritto:
>
>> On Tuesday, February 24, 2015 at 3:23:23 PM UTC+1, riccardo.magliocchetti
>> wrote:
>>
>> I'm no UI/UX expert but modals are more or les
Hi Aron,
Short version - if you're eager to look into this, we're eager to have
composite keys in Django - it's probably one of the last features I can
think of that was discussed for the 1.0 release but we bumped so that "we
can add it for 1.1".
(ahem. :-)
Yes, there have been a lot of changes
? where will
> I get Ideas about what are considered as best practise in django 1.8/+? or
> other suggestions?
>
> Regards
>
> On Sun, Feb 22, 2015 at 6:36 AM, Russell Keith-Magee <
> russ...@keith-magee.com> wrote:
>
>>
>> To my mind, the goal of this projec
nf werkzeug/+webOb in django will let
>>> eliminate some of django's built in way of handling request/response
>>> processing, urlresolving, url routing, view processing some error handling
>>> etc.
>>>
>>> Sould I go for a detail one with what I hav
On Fri, Feb 20, 2015 at 9:29 AM, Diana Probst
wrote:
> The last time I logged into GitHub was at least one computer ago. And
> that computer blew up a bit. I'll try to get on, but this is contingent on
> many factors, and I don't have control over them all. What I will do is
> read the docs on
Hi Andriy,
If we're going down this path, I can't think of any reason we wouldn't
target ever available aggregate. It doesn't need to be all in one patch/PR
- in fact, I'd suggest that unless the implementations are particularly
intertwined, one patch per aggregate (or aggregate group - e.g., all
Hi Marten,
I can understand the motivation, and the approach you've taken makes sense.
It definitely strikes me as a much better alternative to tickets like
#24288 than a setting.
https://code.djangoproject.com/ticket/24288
The DRY issue isn't a huge problem for me - it's certainly ungainly to n
On Sat, Feb 7, 2015 at 12:05 AM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> Hello,
>
> As the test suite is growing, it’s getting slower. I’ve tried to make it
> faster by running tests in parallel.
>
> The current state of my experiment is here:
> https://github.com/django/dj
Hi Elita,
On Fri, Feb 6, 2015 at 1:39 PM, Elita Lobo wrote:
> Hello,
>
> I am a 3rd year student of NIT Durgapur , India as well as a Gnome
> Developer . I have worked on many Python projects as well. I would like to
> start contributing to django.
> Django does not allow bulk_create of objects
On Wed, Feb 4, 2015 at 6:49 AM, frantisek holop wrote:
> Tom Christie, 03 Feb 2015 12:53:
> > Trimming at `request.POST` or at the `Form` layer absolutely isn't
> > sensible, and a `normalize` argument is probably just overcomplicating
> > things, but I got the impression from that ticket that no
On Wed, Feb 4, 2015 at 1:49 AM, Asif Saifuddin wrote:
> Thank you both for the feedback. I will continue my analysis to understand
> django well and also try to contribute some patch on django if I can.
>
>
> For django URL dispatcher improvement I am also looking for some
> suggestions. Should I
On Mon, Feb 2, 2015 at 11:58 PM, Asif Saifuddin wrote:
> Hi Fabio,
>
> Thank you for your project ideas. I'm going to follow the ideas from
> https://code.djangoproject.com/wiki/SummerOfCode2015
>
While this is definitely a safe option, don't rule out a
'not-on-the-official-list' project. The GS
On Mon, Feb 2, 2015 at 11:39 PM, Fabio Caritas Barrionuevo da Luz <
bna...@gmail.com> wrote:
> Some ideas. (which still require approval of the core developers):
>
>
> * Improve database backend base API and related features(including
> introspection feature used by inspectdb), so that it is less
See also 19348 and 8733.
https://code.djangoproject.com/ticket/19348
https://code.djangoproject.com/ticket/8733
My opinion hasn't really changed - my experience has been that Kibi and
Mebi are prefixes that nobody outside standards organisations give a damn
about.
In the example you provide (FIL
On Mon, Jan 12, 2015 at 12:59 PM, wrote:
> On 10/01/15 22:40, Collin Anderson wrote:
>
>> Hi All,
>>
>> In talking to Aymeric and other developers, we're starting to think
>> about the usefulness of global template context_processors. It seems to
>> us that ideally you should only need the "reque
On Mon, Jan 12, 2015 at 10:28 AM, Carl Meyer wrote:
> Hi Russ,
>
> On 01/11/2015 05:20 PM, Russell Keith-Magee wrote:
> >> Without having spent much time to research the consequences — it's on my
> >> TODO list but Collin brought it up before I investigated
On Sun, Jan 11, 2015 at 5:58 PM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> On 11 janv. 2015, at 09:43, Russell Keith-Magee
> wrote:
>
> > However, I'd still have some concerns about a project template that took
> out all the "useful
On Sunday, January 11, 2015, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> On 11 janv. 2015, at 06:20, Russell Keith-Magee > wrote:
>
> > TEMPLATE_CONTEXT_PROCESSORS isn't in the project template at present; it
> is a default value i
On Sun, Jan 11, 2015 at 11:33 AM, Collin Anderson
wrote:
> Hi All,
>
> Based on the early feedback, here's a scaled back proposal:
>
> 1. In the project_template settings.py for new projects:
> - Enable the request context processor
> - Keep the auth context processor
> - Remove the rest (you can
On Sun, Jan 11, 2015 at 6:40 AM, Collin Anderson
wrote:
> Hi All,
>
> In talking to Aymeric and other developers, we're starting to think about
> the usefulness of global template context_processors. It seems to us that
> ideally you should only need the "request" context processor. You could
> e
Hi all,
Following up on my pre-Christmas email - I believe that PR 3114 - the
formalisation of _meta - is now ready to land.
https://github.com/django/django/pull/3114
The code has received a detailed review by several members of the core
team, including Tim, Carl, Collin, and myself; we've had
Hi Alejandro,
On Sun, Dec 28, 2014 at 8:13 PM, Alejandro Dubrovsky
wrote:
>
>
>
> On Sunday, December 28, 2014 7:23:34 PM UTC+11, Alejandro Dubrovsky wrote:
>>
>>
>> On Sunday, December 28, 2014 1:03:26 PM UTC+11, Russell Keith-Magee wrote:
>>>
>>>
On Sat, Dec 27, 2014 at 9:30 PM, Alejandro Dubrovsky
wrote:
>
> Hi all,
>
> When running a small, low traffic site on slow cloud servers (eg
> DigitalOcean), it'd be useful to be able to cache pages, not because the
> site might be taken down from too many request, but to improve
> responsiveness.
Hi Tom,
On Tue, Dec 23, 2014 at 8:23 AM, Tom Christie
wrote:
>
> One thing I'm unclear on: Does the new API contain any (public API) way of
> determining if a relationship has an associated through table?
>
> Entirely possible that I'm being stupid and that's outside the scope of
> the API, but i
On Tue, Dec 23, 2014 at 4:18 AM, Carl Meyer wrote:
>
> Hi Russell,
>
> Many thanks to Daniel, and to you, for all the work on this PR!
>
> On 12/22/2014 12:39 AM, Russell Keith-Magee wrote:
> > * get_fields(include_parents=True, include_hidden=False)
> >
> >
Hi all,
The deadline for 1.8 alpha is rapidly approaching, and one of the features
that has been proposed for inclusion is Daniel Pyrathon's GSoC project
refactoring the _meta object.
A huge thanks to Tim, Carl, Collin, Loïc, Anssi, and everyone else that has
provided detailed reviews and feedbac
On Sun, Dec 21, 2014 at 10:33 PM, Josh Smeaton
wrote:
>
> Would you mind linking to the ticket you're talking about? Will encourage
> more people to participate if they don't have to search Trac for it ;)
>
He did - as an inline link:
https://code.djangoproject.com/ticket/23780
Yours,
Russ Mage
On Sun, Dec 21, 2014 at 6:38 PM, Riccardo Magliocchetti <
riccardo.magliocche...@gmail.com> wrote:
>
> Hello,
>
> Il 20/12/2014 20:40, Tim Graham ha scritto:
>
>> You can also see other tickets we are targeting for 1.8 with this
>> filter. This includes some of the remaining large features as well
On Thu, Dec 18, 2014 at 7:48 AM, Carl Meyer wrote:
>
> On 12/17/2014 04:39 PM, Russell Keith-Magee wrote:
> > On Thu, Dec 18, 2014 at 5:03 AM, Aymeric Augustin <
> > aymeric.augus...@polytechnique.org> wrote:
> >
> >> On 17 déc. 2014, at 21:54, Carl Meyer
On Thu, Dec 18, 2014 at 5:03 AM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> On 17 déc. 2014, at 21:54, Carl Meyer wrote:
>
> > So I think there is a backwards-compatibility issue.
>
> Indeed.
>
> > Personally, I would love to decide to just bite this bullet and
> > normalize
Hi Rune,
I agree with Tim. This is clearly a problem that exists, and I agree it
would be good to fix it. However, I wouldn't want to see this as an "Admin
only" fix.
I'd rather see a generic hook that Admin then leverages as the "first
customer". A similar approach was taken with object-level pe
On Mon, Dec 8, 2014 at 7:49 AM, Michael Manfre wrote:
>
>
> On Sun, Dec 7, 2014 at 6:37 PM, Russell Keith-Magee <
> russ...@keith-magee.com> wrote:
>
>> * The corollary of this last point is that the release *before* a stable
>> release can't have
On Sun, Dec 7, 2014 at 6:35 PM, Shai Berger wrote:
> I like the general idea of experimental API, although Carl and Aymeric's
> notes
> are important: If we do this, we need to very picky in its use, or else it
> just becomes an easy route to avoid committment. In particular, there
> should
> be
HI Anshuman,
On Mon, Oct 20, 2014 at 2:03 PM, Anshuman Aggarwal <
anshuman.aggar...@gmail.com> wrote:
> Hi Russ,
> Notwithstanding the performance, the current solution of doing 1000
> updates in a single transaction using ORM appears to be (in pseudocode
> below):
>
>
>
>
>
>
> as oppos
Hi Anshuman,
As I mentioned when you raised this issue 2 days, ago:
https://groups.google.com/d/msgid/django-developers/bac70fe2-3bbb-45c9-b805-5469e89f2754%40googlegroups.com?utm_medium=email&utm_source=footer
if you can provided evidence to back up your claim, I'll reverse my
position on the n
Hi Anshuman,
On Sat, Oct 18, 2014 at 2:05 PM, Anshuman Aggarwal <
anshuman.aggar...@gmail.com> wrote:
> Please see this enhancement request:
> https://code.djangoproject.com/ticket/23646
>
> Unlike what Russ has suggested, I'm pretty sure that a single UPDATE query
> with a large number (Ks/Ms) o
On Thu, Oct 2, 2014 at 3:04 AM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> Hello,
>
> I've been thinking about providing built-in support for Jinja2 in Django.
> I found that supporting pluggable template engines, like Django does for
> databases, caches, etc. would be the mos
Hi Justin,
On Tue, Sep 23, 2014 at 7:10 AM, Justin Holmes
wrote:
> Currently, we perform a sanity check to provide a useful error message
> if a view returns None:
>
>
> https://github.com/django/django/blob/1101467ce0756272a54f4c7bc65c4c335a94111b/django/core/handlers/base.py#L138
>
> However,
Hi Aymeric,
As I recall, the reasoning was:
a) CSRF should almost always be on anyway
b) The cost of having the CSRF token in place if you actually aren't using
CSRF was pretty low
c) Template documentation essentially says "put {% csrf_token %} in your
template always; if it's hardcoded, there
dards; this is an opportunity for us to change that
trend.
Yours,
Russ Magee %-)
-- Forwarded message --
From: Robert Collins
Date: Sat, Sep 20, 2014 at 6:00 AM
Subject: HTTP/2 and WSGI
To: graham.dumple...@gmail.com, russ...@keith-magee.com, chr...@plope.com,
armin.ronac...@active-
o X" by sending mail to
"django-developers@" was asking for trouble.
I've just rolled out this change, along with Daniele's suggested tightening
of the description text.
Thanks everyone for your suggestions and contributions.
Yours,
Russ Magee %-)
On Fri, Sep 19, 201
On Fri, Sep 19, 2014 at 5:39 AM, Wim Feijen wrote:
> Hi Russell,
>
> Is this an issue we should solve?
>
> Because I believe technology can help here. For example, by posing a
> question when a user is creating a ticket. Ask if it deals with security;
> then present two clear buttons: "Report a s
;
> Did you manage to speak to the technical board about renaming the group?
>
> Wim
>
> On Tuesday, 9 September 2014 03:49:21 UTC+2, Russell Keith-Magee wrote:
>>
>>
>> On Mon, Sep 8, 2014 at 11:24 PM, Carl Meyer wrote:
>>
>>> On 09/08/2014 08:56 AM
On Thu, Sep 11, 2014 at 6:11 AM, Andrew Pinkham wrote:
> Hi,
> I am not qualified enough to express an opinion on the matter of the DCoC.
> However, I have a few questions:
>
> - Have we consulted a psychologist or a specialist on the topics of
> community inclusion and protection? Their knowledg
1 - 100 of 2854 matches
Mail list logo
