Re: Django Async DEP

Congratulations, and great news! I hope the TB will consider sharing details and/or a summary of the "long and involved vote"; I'll bet there's a bunch the broader community could learn from the specifics. Jacob On Sun, Jul 21, 2019 at 3:54 PM Andrew Godwin wrote: > Hi everyone, > > After a lo

Re: Pre-proposal: adopt dj-database-url as a DEP 7 official project

Puling together a few things: On Jul 18, 2019, 3:13 PM -0400, Kevin Grinberg , wrote: > I've more commonly found myself using pypi.org/project/dsnparse/ more often > than dj-database-url, due to support for DSNs in setting CACHES (with Heroku > Redis > for example, you get a REDIS_URL exposed th

Pre-proposal: adopt dj-database-url as a DEP 7 official project

Hi folks - I’d like to gauge interest in adopting dj-database-url (http://github.com/jacobian/dj-database-url) as an official project (https://github.com/django/deps/blob/master/final/0007-official-projects.rst). This is my pre-proposal. I think dj-database-url is very widely-used, and scratches a

Help wanted reviewing applications for the DSF internship

Hi folks - I'm looking for some folks to help me review applications for the internship to build a new DSF membership app. If you have experience hiring junior developers and can devote around 10+ hours over the next few weeks. Background: the DSF put out a CFP

Re: Django channels advice

Hi, Unfortunately, we can't help you here -- sorry! This list is dedicated to the discussion of developing Django itself, not answering usage questions. You might try the django-users group ( https://groups.google.com/forum/#!forum/django-users), or StackOverflow. Good luck, Jacob On Thu, May 2

Re: Proposal: security enhancements

Great ideas, James. I totally agree we shouldn't rest on our laurels, and love the goal of pushing things forwards. Overall, I'm not sure a DEP is needed: each of these things is fairly small and tightly scoped, can be implemented on its own, and provides value independent of the whole. That seems

Re: Fellow Report — January 12, 2018

Hooray, welcome Carlton! Looks like a great first week; glad to have you! Jacob On Fri, Jan 12, 2018 at 9:01 AM, Carlton Gibson wrote: > Hi all, > > With help from Tim, Aymeric and Frank, I got started on the fellowship > this week. > (Thank you all!) > > > I've Reviewed Patches on: > > https:/

Re: Default to BigAutoField

I think this would be a good improvement, and I'd like to see it. I've been bitten by integers overflowing at least twice I can remember in my career, which is two times too many. However, a major thing we'd have to work out is the upgrade path Consider a simple model: class Person(Model):

Re: In-memory queryset

Hey Paul - There are a couple of implementations I'm aware of: https://github.com/stphivos/django-mock-queries https://github.com/dcramer/mock-django Neither are a complete implementation of the QuerySet API, and I think this is because the QuerySet API surface is _huge_. Implementing the entire

RFC: DEP 7 - dependency policy

Hi all - DEP 7 proposes a new dependency policy. In a nutshell, the policy is: Python packaging is good now. Django can have dependancies. For full details, please check out the DEP: https://github.com/django/deps/blob/master/draft/0007-dependency-policy.rst I'd appreciate any comments and feedb

Re: DEP pre-proposal for a simpler URLs syntax.

Hi Tom - Thanks for putting this together! Overall, +1 from me as well: I've taught Django to a bunch of beginners, and URLs are one of the major pain points. I'd love to make them easier, and your proposal looks pretty dang great. Some specific feedback: 1. I'm not too thrilled on the "is this

Re: change commit message format to present tense?

I'm not entirely sure because my memory sucks, but odds are that I started the current standard of using past-tense. FWIW I no longer care even at all, I think as long as commit messages are clear we I don't care what tense they are. Following the standard git way seems totally OK to me. Jacob O

Re: Call for Channels work

Hi Tom - This is a great question, and thanks for asking it. The short version is "we're not quite sure yet, and we need to work this bit out." To go into more details, first I need to explain a bit about how the MOSS committee (of which I'm a part) works, and what it is and isn't doing. Specifi

Re: Rewriting admin internals

Hi Asif - I don't think a DEP is the right approach. The problem isn't a controversial feature or a hard-to-design-API; it's that this is going to take a lot of time or money, and probably both. Writing a DEP won't answer the question of "how the heck are you going to find a half-dozen people who

Re: Rewriting admin internals

Hi Asif - You're probably noticing some pushback already, so I want to give you some background as to why that's the case. The admin may look simple on the surface, but it's shockingly complex and represents a ton of work. The original version was the work of a whole team (Simon, Adrian, Wilson,

Re: GitHub Issues for DEP repository?

On Wed, May 11, 2016 at 1:11 PM, Carl Meyer wrote: > So I'd personally be > fine with a PR to amend this section to remove mention of private > contact. Jacob, I think you wrote this (or adapted it from PEP 1) -- any > thoughts? > I don't recall why that's in there; I'm guessing it came over ver

Re: Process DEP for "official" non-core projects

On Wed, May 11, 2016 at 2:29 PM, Andrew Godwin wrote: > I would be inclined to merely mark it as deprecated and not drop it from > e.g. the GitHub org, though, as where would we move it *to*? > Sure, that's fine with me too. The key point is just that we're not (implicitly or explicitly) offerin

Re: Process DEP for "official" non-core projects

I like this, and +1 on your rough outline. There is one missing thing here though: I think we need to consider the process/policy for removing things if they're no longer maintained. Without clear maintainership forks happen, which is bad for pretty much everyone. So I think we should have a plan

Re: My Take on Django Channels

On Thu, May 5, 2016 at 7:22 PM, Carl Meyer wrote: > I think channels, multiple-template-engines, and > reworked-middleware (and migrations, for that matter) are all > rethinkings of long-standing core aspects of how Django works, which in > my mind makes them prime DEP candidates, > There seems

Re: Django Integration

On Wed, May 4, 2016 at 2:45 PM, Marc Tamlyn wrote: > Major features merged into Django have generally never been as "perfect" > as the standards required for smaller patches. There's a recognisation of > the need for ongoing work, probably over the course of multiple versions, > in order to perfe

Re: Post-Mortem of the djangoproject.com outage earlier today.

Thanks for the info, and for the quick fix! Jacob On Wed, May 4, 2016 at 3:48 AM, Florian Apolloner wrote: > Hi, > > earlier today (roughly 9:30 UTC) I deployed a wrong (local) branch from > our ansible repository to dp.com. This branch included our old (now > expired) gandi SSL certificate. On

Re: Feedback on Django Channels

I do think encrypting the Redis channel layer is something we should offer: Redis out of the box doesn't do transport-layer encryption, which is going to make Channels a hard sell to anyone with any for of regulatory/compliance requirements. [1] I think probably Fernet [2] is the right way to do t

Re: Feedback on Django Channels

On Thu, Mar 17, 2016 at 1:44 PM, Florian Apolloner wrote: > Yes, this seems like a major pain point, especially since the routing does > not scale if you add another app, ie you need to add a wrapper which then > dispatches to the individual connect routines. In a best case scenario I'd > just ha

Feedback on Django Channels

Hi folks (and especially Andrew): I've just completed writing an example Channels app [1] for an article about Channels [2]. Overall it was a super-pleasant experience: Channels seems pretty solid, the APIs make sense to me, and I couldn't be more excited about the new things this'll let me do! I

Re: adding to documentation

Hi Becka - I'm glad you figured it out, and even happier that you'd like to contribute to making the docs better! Fixes to the docs where you found problems/errors are certainly welcome; you can do that in a ticket or a pull request, which ever you find easier. There's some information about how

[Re]launching DEPs

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

Re: Updating the organization of the Django Project

+1. Aymeric, I can't thank you enough for taking this on and running with it. Jacob On Fri, Jul 25, 2014 at 7:20 AM, Chris Foresman wrote: > As a non-core community member, I welcome a streamlined way for new > potential coders to contribute. > > > On Thursday, July 24, 2014 7:02:16 AM UTC-5,

Re: Solving the select+1 problem.

I'm not great at Haskell, either, but this looks to me to be very similar to prefetch_related ( https://docs.djangoproject.com/en/dev/ref/models/querysets/#prefetch-related ). Jacob On Wed, Jun 11, 2014 at 6:15 AM, Jonathan Slenders < jonathan.slend...@gmail.com> wrote: > The "select+1" problem

Re: Make url patterns group kwargs more simple

On Wed, May 28, 2014 at 2:51 PM, Marc Tamlyn wrote: > I'm not saying any of this is not currently possible - it is. But I'd > prefer to introduce a stable, robust API and then look at exact > implementations of format. > > I completely agree -- rather than pick something from a bunch of good opti

Re: That's enough.

I'm sorry you feel that way, Cal; your contributions have been appreciated, and I've personally appreciated having you around. Thanks for all you've done. If you ever feel up to sharing with me more specifics, so perhaps we can try to change things to be more welcoming to contributions, well, you

Re: "Master/slave terminology"

Meira, your position has been made abundantly clear, and now your behavior is treading dangerously close to the line. I'll remind you and others of our community's code of conduct (https://www.djangoproject.com/conduct/), which specifically requires that we be welcoming, friendly, patient, and resp

[Announce] Django security releases issued

Today we've issued releases to remedy three security issues reported to us. Affected versions are Django 1.4, Django 1.5, Django 1.6 and the Django 1.7 beta. Full details and download information are on the Django project weblog: https://www.djangoproject.com/weblog/2014/may/14/security-releases

[ANNOUNCE] Django 1.6.2 and Django 1.7a2

Hey y'all -- We've just released Django 1.6.2, the latest bugfix release in the 1.6 series, and Django 1.7a2, the second alpha preview of the upcoming 1.7 release. As usual, more details are available on the blog: https://www.djangoproject.com/weblog/2014/feb/06/django-162-and-django-17a2-relea

Re: Django Security & OWASP Project

Hey Michael -- This sounds right up my ally. I'll jump on the list and post some more info over there. Jacob On Tuesday, January 14, 2014, Michael Coates wrote: > Django Developers, > > Hello! Over at OWASP I've started a framework security project. Our goal > is to capture the security postur

[ANNOUNCE] Django 1.6.1 released

Hey folks -- We've just released Django 1.6.1, a bugfix release for last month's Django 1.6 release. More details are in our blog post: https://www.djangoproject.com/weblog/2013/dec/12/django-161/ and in the release notes: https://docs.djangoproject.com/en/1.6/releases/1.6.1/ Enjoy!

Security Advisory: ImageField abuse

Hi folks - We've just published a short security advisory about ImageFields: https://www.djangoproject.com/weblog/2013/dec/02/image-field-advisory/ ImageField expects a valid image file, but depending on your app it may allow uploads on non-image content, such as HTML or JavaScript. Unfortun

[Announce] Expected djangoproject.com downtime tomorrow, Oct 18, starting 20:00 UTC

Hi folks - We'll be doing some work on djangoproject.com (and associated sub-sites) tomorrow, starting around 20:00 UTC. Expect some downtime, possibly as long as an hour or so, starting around then. During the downtime, as usual, you can find a mirror of Django's documentation on Read the Docs:

Re: Need Django Expert for short project (moving a website)

Hey Matt - Unfortunately, we can't help you. You've reached the django-developers mailing list, a group devoted to talking about the development *of* Django, not *using it*. I can understand the confusion, and I'm sorry to have to send you elsewhere, but the right place for this is the django-use

[ANNOUNCE] Security releases issued (1.4.6, 1.5.2, 1.6b2)

Hi folks -- Today the Django team is issuing multiple releases -- Django 1.4.6, Django 1.5.2, and Django 1.6 beta 2 -- as part of our security process. These releases address two cross-site scripting (XSS) vulnerabilities: one in a widget used by Django's admin interface, and one in a utility func

Re: Deprecation a little harsh?

I'm sorry; I was snarkier and nastier than I should have been (and than I intended to be). Thanks for calling me on it; I'll try to do better next time. Jacob On Tue, Aug 13, 2013 at 10:03 AM, Andre Terra wrote: > On Tue, Aug 13, 2013 at 9:22 AM, Jacob Kaplan-Moss wrote: > &

Re: Deprecation a little harsh?

On Tue, Aug 13, 2013 at 1:37 AM, Chris Wilson wrote: > I would love to see support extended for a bit longer after deprecation. This is a matter of resources; we struggle to maintain security releases against 3 simultaneous releases (e.g. right now 1.4.x, 1.5.x, and the up-coming 1.6). Adding a

Re: Deprecation a little harsh?

Hi Simon - Here's the thing: I'm sensitive to the fact that you think we're moving too fast, but you have to understand that we also hear that we're moving too *slow*. We have to strike a balance, and I'm happy where we've struck that balance. If you'd like to help push us closer to where *you* t

Security Advisory: BREACH and Django

Hi folks -- At last week's Black Hat conference, researchers announced the BREACH attack (http://breachattack.com/), a new attack on web apps that can recover data even when secured with SSL connections. Given what we know so far, we believe that BREACH may be used to compromise Django's CSRF prot

Re: Proposal: Modifying the CSRF protection scheme

Hey Shai - I have no objections to this change. I think it's got a slight whiff of security theatre, in that it *looks* like it adds more protection than it *actually* does. However, I, too, have spent a ton of time talking auditors down from "OMG Django is vulnerable to CSRF!" and I'd like to do

Re: Hybrid Property request

On Tue, Jul 16, 2013 at 8:04 PM, Russell Keith-Magee < russ...@keith-magee.com> wrote: > So - functionally, what you describe can be done. What's missing is > someone to polish the concepts into a patch for inclusion into Django's > repository. If this is something that interests you - get hacking

Re: Deprecate FCGI support in Django 1.7

On Mon, Jul 15, 2013 at 4:31 PM, Florian Apolloner wrote: > Also, if we move it outside of django-core we can send a good signal that > FCGI in Django is basically "Use at your own risk" (which it is already if > you ask me). > This, for me, is the key: anything that's not a WSGI container is bas

Re: Revisiting multiline tags

On Mon, Jul 15, 2013 at 1:34 PM, Daniel Ellis wrote: > Is it considered gauche to revive old topics such as this? It's not, but my opinion hasn't changed -- I'm still -1, and so's Adrian. So unless you've got something really convincing, an argument that hasn't been presented yet that is totall

Re: Django 1.5.2

Hey Michael - We don't have a schedule for 1.5.2 at the moment, but I'll take a look and see if I can get a release out sometime soon. No promises, but I'll do my best. Jacob On Tue, Jul 9, 2013 at 11:00 AM, Michael Mior wrote: > Just wondering if there's an ETA on Django 1.5.2. Currently ther

Re: ANNOUNCE: Django 1.6 beta 1 released

Yes it should! The FAQ also needs to be updated. Jacob On Fri, Jun 28, 2013 at 9:04 AM, Ned Batchelder wrote: > > On 6/28/2013 9:48 AM, Jacob Kaplan-Moss wrote: > >> Hi folks -- >> >> I'm pleased to announce that we've just released Django 1.6 beta 1, &

ANNOUNCE: Django 1.6 beta 1 released

Hi folks -- I'm pleased to announce that we've just released Django 1.6 beta 1, the second in our series of preview releases leading up to Django 1.6 (due in August). More information can be found on our blog: https://www.djangoproject.com/weblog/2013/jun/28/django-16-beta-1-released/ And in t

Re: Status of localflavor recombination

Thanks for doing this! That's a lot of not-entirely-fun grunt work, thanks for making it happen. Jacob On Sun, Jun 9, 2013 at 6:33 AM, Jannis Leidel wrote: > Hi all, > > I'm writing you today to report on the status of the recombination of the > localflavor app I've proposed a little while ago

Re: Recommending a Python 3-compatible MySQL connector

I've reached out to a lawyer friend to see if he can give us some guidance. Until then, let's avoid making a recommendation either way. Jacob On Wed, Jun 5, 2013 at 10:01 AM, Aymeric Augustin wrote: > 2013/5/10 Aymeric Augustin >> >> > Also actively developed by @geertjanvdk at Oracle so he may

Re: Meta-Proposal: Write *above* quotations in mailing list replies

Can we PLEASE not have this argument? It's literally as old as email itself, and totally futile. Drop it. Now. Jacob On Tue, Jun 4, 2013 at 2:33 PM, Wim Lewis wrote: > > On 4 Jun 2013, at 12:00 PM, Daniele Procida wrote: >> * quote what needs to be quoted for context >> * don't quote anything t

Re: Make sure QuerySet.get() does not fetch more rows than it absolutely needs

On Tue, Jun 4, 2013 at 1:48 AM, Anssi Kääriäinen wrote: > As for .get() - I don't find the number of duplicates in the error > message that useful. Yeah, I'd agree with that. It's another one of those things that goes WAY back into the misty reaches of Django's history, but I don't think there's

ANNOUNCE: Django 1.6 alpha 1 released

Hi folks -- I'm pleased to announce that we've just released Django 1.6 alpha 1, the first in our series of preview releases leading up to Django 1.6 (due in August). More information can be found on our blog: https://www.djangoproject.com/weblog/2013/may/26/django-16-alpha-1/ And in the re

Re: Predicate as suggested new feature to extend url resolver process

url resolution to application state . This could have negative >> implications, especially for performance. On top of that, the same >> functionality could be achieved by creating a function/class to route >> the request further after django has initially routed the request

Re: Predicate as suggested new feature to extend url resolver process

I'm not sure I understand what you're proposing here. How is this different from @require_GET, @require_POST, and friends? Jacob On Wed, May 22, 2013 at 11:05 AM, Rach Belaid wrote: > I just did a pull request resulting of my last Django sprints for > adding a new feature in Django. > > https://

Re: first() and last(), earliest() and latest()

On Tue, May 21, 2013 at 10:45 AM, Anssi Kääriäinen wrote: > I just pushed the patch to master. I didn't do anything to the API in > the latest pull. No only=True or .only(), and earliest() and latest() > still exist. I didn't feel like bikeshedding this issue any more. > > I am happy that we now h

Re: Combine localflavor apps again

On Tue, May 21, 2013 at 7:51 AM, Jannis Leidel wrote: > What do you think? I have no opinions either way, happy to help out if this is the direction you want to go. Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe fro

Re: I am interested in maintaining django-localflavor-us

OK, you should be good to go. Jacob On Mon, May 20, 2013 at 11:54 PM, Trey Hunner wrote: > I'm treyhunner on Github. Thanks Jacob. > > > On Monday, May 20, 2013 3:14:59 PM UTC-7, Jacob Kaplan-Moss wrote: >> >> No objections from me. What's your GitHub usern

Re: I am interested in maintaining django-localflavor-us

No objections from me. What's your GitHub username? I'll hook you up. Jacob On Mon, May 20, 2013 at 3:10 PM, Trey Hunner wrote: > The django-localflavor-us package currently lacks a responsive > maintainer. I would like to fix this problem by helping to maintain > this project. > > My primary g

Re: Model field validation (of the field itself, not values)

Hey Luke - Yup, this is indeed a problem. It's actually the subject of a Summer of Code proposal [1], so if you can wait there's a good chance that you won't have to do any work yourself :) Jacob [1] https://groups.google.com/forum/#!msg/django-developers/e0-rOIkrXaQ/w5aiW_R6aFYJ On Sat, May 1

Anyone have ideas on #16550 - custom SQL before/after syncdb?

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

Re: Perception of attitude in tickets

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

Re: Perception of attitude in tickets

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

Re: djangoproject.com is down

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

djangoproject.com is down

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

Re: Perception of attitude in tickets

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

Re: Perception of attitude in tickets

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

Re: Perception of attitude in tickets

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

Re: reconsider re-opening ticket 901

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

Re: test discovery

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

Re: [GSoC 2013] contribute to django-deployer for deploying django to PaaS easily

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

Fwd:

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

Re: Django 1.6 release timeline

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

Re: GSoC proposal for the "Adding New Feature of Dynamic Forms and Enhancement of Django-forms"

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

Re: GSOC: Deadline soon!

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

Django 1.6 release timeline

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

Re: [GSoC 2013] Revamping validation functionality proposal

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

Re: [GSoC 2013] Revamping validation functionality proposal

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

Re: Problem with creating a one-to-one instance

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

Re: [GSoC 2013] Improving code quality

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

Re: Proposal: Redefine specific {% block %} in an intermediate template

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

Re: [GSoC 2013] Revamping validation functionality proposal

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

Re: websockets

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

Re: Support for WSGI applications within Django (Ticket #12091)

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

"Design Decision Needed" is gone. Good riddance.

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;

Re: Epydoc failed to generate documentation for Django 1.5

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

Re: Django 1.5.1 released

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

Re: URL dispatcher fallthrough?

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

Re: URL dispatcher fallthrough?

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

[ANN] Django 1.5.1 released

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

Re: Policy for stable/1.x.x branches

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

Re: Policy for stable/1.x.x branches

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

Re: What can I do to get feedback on my pull request?

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

Re: What can I do to get feedback on my pull request?

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

Re: Changes to django's settings module

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

Goodbye, Malcolm

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.

Re: Good practices for production settings

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

Re: Proposal: deprecate and remove django.contrib.comments

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,

  1   2   3   4   5   6   7   8   9   10   >