Administrative note about 1.1 beta

Hi folks -- We'll be releasing 1.1 beta 1 shortly; look for the announcement from James. However, there are two tickets that didn't make it into the release that we're going to grant a special dispensation from feature freeze: First is #3182, queryset.update()/update_or_create(). This didn't ge

Django 1.1 beta 1 released

Hi all -- Tonight we've released Django 1.1 beta 1, the second in a series of alpha and beta preview packages running up to the final Django 1.1 release, due mid-April. As always, alpha and beta packages are *not* for production use, but if you'd like to try out the new features or go bug-hunting

Django 1.1 beta 1 released

Hi all -- Tonight we've released Django 1.1 beta 1, the second in a series of alpha and beta preview packages running up to the final Django 1.1 release, due mid-April. As always, alpha and beta packages are *not* for production use, but if you'd like to try out the new features or go bug-hunting

Re: New Feature: ModelBase Signals

On Tue, Mar 24, 2009 at 10:41 AM, Dan wrote: > I think an easy solution would be to use signals to allow receivers to > be notified when the class type is being declared in > ModelBase::__new__ and receive an alterable copy of the class > declaration.  Is this sort of thing something that would m

Re: Call for ideas: Admin Improvements

On Tue, Mar 31, 2009 at 8:30 AM, Russell Keith-Magee wrote: > It would be _exceedingly_ unwise to advise any student to base a GSoC > proposal on the use of JQuery (or any other framework, for that > matter). D'oh. The reason that Zain is including use of jQuery in this proposal is because I, e

Re: Call for ideas: Admin Improvements

On Tue, Mar 31, 2009 at 9:43 AM, Russell Keith-Magee wrote: > I'm in full agreement that "Improving the admin UI" is certainly a > good pre-proposal, and I'm sure there's plenty of tickets that could > fill a SoC. My concern is that "move to using jQuery" isn't a good > line item in a proposal wi

Re: CSRF template tag patch done

Hi Luke -- I'm sorry it took me so long to review this patch, but I wanted to make sure I knew what I was talking about first. What you've done here is admirable, and I agree that the goal of out-of-the-box CSRF protection is important, but ultimately I can't get behind committing this. It's si

Re: GSoC 2009: Testing Upgrades/Awesomeness

On Tue, Mar 31, 2009 at 8:52 PM, Russell Keith-Magee wrote: > I like the sentiment and the goal - my only concern is the extent to > which this is in scope for a Django GSoC project. If making this > integration requires changes on the Django side, you're fine - but if > you need to make changes

MySQL test failure

Hi folks -- I'm seeing a single test failure on MySQL 5.0 """ == FAIL: Doctest: regressiontests.model_inheritance_regress.models.__test__.API_TESTS -- Tracebac

Re: Follow-up to "contrib.admin is slow with large, complex datasets"

On Sun, Apr 5, 2009 at 4:52 PM, mrts wrote: > [...] Can you please stop? We all get that you think these tickets are important. They're on the milestone for 1.1, so they'll be fixed. Nagging us here doesn't help get your tickets pushed to the front of the queue. Jacob --~--~-~--~~-

Heads up: backwards-incompatible change to admin actions

Hi folks -- A quick heads-up to anyone already developing admin actions against 1.1 beta: Because of a few bugs in the design of admin actions, I've needed to make a small backwards-incompatible change to the signature of action functions. If you've been defining actions as methods on your Model

Re: AttributeError when running test against PostgreSql 8.4beta1

On Wed, Apr 15, 2009 at 7:48 PM, Horacio de Oro wrote: > Is this a bug? Should I file a bug report? Yes, please do. Thanks! Jacob --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post

Summer of Code 2009

Kevin Kubasik, "Upgrade the Awesomness Quotient of the Django Test Utils and Regression Suite" Mentor: Eric Holscher Christopher Cahoon, "Improved HTTP and WSGI Support" Mentor: Malcolm Tredinnick Zain Memon, "UI improvements for the admin interface" Mentor: Jacob K

Re: Summer of Code 2009

On Mon, Apr 20, 2009 at 3:12 PM, Waylan Limberg wrote: > And yet I only count 5. Looks like you missed: > > Alexander Gaynor, "Multiple Database Support in Django" > Mentor: Russell Keith-Magee Either I had a copy/paste foul or else I'm messing with Alex's head. Take your pick :) Jacob (Congra

Re: For QuerySet qs, list(qs)[k] does not always equal qs[k]

On Fri, Apr 24, 2009 at 9:09 AM, David Gouldin wrote: > Lest you criticize accessing all queryset items by index, Django is > currently doing just that in > django.forms.models.BaseModelFormSet._construct_form.  This means that > when creating an inline for a model without an order_by, Django can

Re: My Proposal [GSoC '09 Admin UI Improvements]

2009/4/24 Jeremy Dunck : > I'm not sure what this means.  Inline order is defined by the > underlying queryset, isn't it?  What would reordering them on the > client do in the DB? This is a return of and a cleaning up of the old order_with_respect_to (which still sorta works, but the admin featur

Re: GSoC Intro, Update, and Proposal -- HTTP & WSGI Support Improvements

On Fri, Apr 24, 2009 at 7:53 PM, Graham Dumpleton wrote: > That shouldn't be the case. Supporting X-Sendfile was I recall > actually an after thought. The original intent was to be able to make > use of mod_python req.sendfile() or WSGI wsgi.file_wrapper mechanisms. Right; I think the idea shoul

Re: GSOC process

On Sat, Apr 25, 2009 at 9:12 AM, mrts wrote: > To get more visibility and community input for the scope of GSOC > projects, let me propose the following workflow. The time to suggest this was months ago when the GSoC process *began*, and the *place* to do it was on the GSoC mailing list, not her

Re: GSOC process

On Sat, Apr 25, 2009 at 9:39 AM, mrts wrote: > As an example I've tagged a couple of tickets with gsoc09-admin- > refactor: Please don't do that. You're effectively trying to order Zain to do some work without consulting him, me (his mentor), or anyone else first. Further, it appears you haven'

Re: Job: Python Web Developer, SF, CA (locals only)

On Mon, Apr 27, 2009 at 5:35 PM, SrRecruiter wrote: > Python Web Developer [...] Please direct job posts to django-users; django-dev is for discussion of developing Django itself. Jacob --~--~-~--~~~---~--~~ You received this message because you are subscribed t

Re: Django 1.0 and Django SVN side by side?

On Wed, Apr 29, 2009 at 5:08 PM, Andrew Smith wrote: > Sorry, this is probably a silly question but I'm fairly new to > python/django. Is it possible to have django 1.0.x and the svn version > installed side by side and if so, how do I achieve this? PYTHONPATH is what you want to learn about her

Re: New to open source dev

On Tue, May 5, 2009 at 10:24 PM, Joshua Russo wrote: > I have been tinkering with some custom objects for db fields, form > fields, and widgets and have seen one or two things that might be nice > enhancements to the base objects. How exactly does the process of > contributing work? Glad you're

Re: Reduce bug triage overhead: DjangoAwesomeBot

On Tue, May 5, 2009 at 11:56 PM, Almad wrote: > Cool for me, but have enough pet projects so now, but if anyone have > spare weekend to implement it? :) Unfortunately, Anyone doesn't have a lot of free time these days (nor does his brother, Someone). No, but on a serious note: ideas are cheap;

Django 1.1 update

Hi folks -- The EuroDjangoCon sprints have started, and we're hacking hard to get 1.1 out the door. Here's the plan: I'm hard at work punting tickets out of the 1.1 milestone. It's tough to do, but this is what time-based releases mean: sometimes you have to ship with known issues. Now, we can'

Re: Django 1.1 update

On Thu, May 7, 2009 at 1:09 PM, Marty Alchin wrote: > While I still think that's a valuable feature, and will likely be > required in order to complete Honza's model validation work for GSOC, > it's really a new feature that has so far caused far more bugs than > it's worth. I'd like to recommend

Re: Django 1.1 update

On Thu, May 7, 2009 at 12:43 PM, Jacob Kaplan-Moss wrote: > I'm hard at work punting tickets out of the 1.1 milestone. It's tough > to do, but this is what time-based releases mean: sometimes you have > to ship with known issues. Update: I've pushed/closed all the issues

Posting to the wrong list (was: Re: Need Django Developer urgent)

On Fri, May 8, 2009 at 12:59 PM, Joshua Partogi wrote: > Some people get confused and thought that this list is for people that > develop apps with django :-D Those people might want to take the time to read the list description (http://groups.google.com/group/django-developers) that they see wh

Re: Application developed using Django

Hi Marc -- In general this isn't exactly the right place for these questions -- some would be better put to django-users since they're questions about *using* Django, not developing it, and others would more appropriately be directed to the DSF (http://www.djangoproject.com/foundation/). However

Re: Security bug in Django?

Hey Stephen -- Sorry 'bout that: because we publicize the security@ address it gets lots of spam, and your message got filtered by mistake. I'll look it over this morning and get back to you. Thanks for the reminder! Jacob --~--~-~--~~~---~--~~ You received this

Re: Offering sponsorship to work on improving Django

Hi folks -- Two things: First. This is quickly getting off-topic. If someone wants to try to take Andy up on his offer they should contact him off-list. Second, if it sounds too good to be true, it probably is. I have reason to believe we're being trolled here. So again, please take it off-list

Re: 1.1rc1 - KeyError in debug.py in technical_404_response

On Mon, Jul 27, 2009 at 7:48 AM, John P. Speno wrote: > Then ran the server using manage.py runserver. > > telnet localhost 8000 > > typed and entered: GET foo HTTP/1.0 > > And the exception is raised. Trying to GET any resource that doesn't > begin with a slash raises this exception. Unless I'm

Re: Two simple to fix bugs in 1.1 RC

On Mon, Jul 27, 2009 at 6:03 AM, Russell Keith-Magee wrote: > To remove any illusions here - v1.1 won't be bug free. If we're ever > going to put out a release, we have to hold our nose and acknowledge > that some bugs are going to exist in the final release. For the record: I'm fine shipping 1.1

Re: [GSOC] Altering the signature of Field.db_type and Field.get_db_prep_*

Hi Alex, Russ -- I see some good pros and cons of each your suggestions. Just to throw some more fuel on the fire, though, I've got an idea of my own: I tend to slightly favor introspection to identify old-style fields -- it makes it easy to raise warnings/errors at the right point, for one -- b

Re: Long-term direction for shortcuts

On Sun, Aug 2, 2009 at 8:05 PM, Brent Hagany wrote: > But, just to be explicit, I don't want to > limit the discussion just to that patch, or to render_to_response or > any particular shortcut.  First, we should discuss the larger issue of > whether technically unnecessary code (which is what any

Re: Template Caching

Hi Mike -- Ah, it looks like my strategy of "wait for someone else to reply and hope that he sums up my feelings so that I don't have to bother" has worked perfectly. Thanks, Russ! [IOW: I agree completely with Russ.] I'll be digging into this patch in some detail, but based on what I've seen s

Re: Allowing single values instead of tuples for choices in ChoiceField

On Fri, Aug 7, 2009 at 10:37 AM, gruszczy wrote: > The issue is that I consider convenient being able to pass a list of > either tuples or single objects for choices list in forms ChoiceField. > The engine would itself detect non-tuple values and turn them into two- > tuples. There are some good p

Re: 1.2 Proposal: Add a few more tutorial steps

On Fri, Aug 7, 2009 at 11:19 AM, Rob Hudson wrote: > I'd be happy to help flesh out one or more of these.  This isn't > necessarily a 1.2 feature but would be a nice addition to the > documentation. I am *always* looking to improve the docs, so of course I'm an enthusiastic +1 on more tutorials.

Re: App Engine support

On Mon, Aug 10, 2009 at 9:07 PM, Malcolm Tredinnick wrote: > The only that seems to be possibly *required* to be changed in Django to > support app-engine as a storage backend is the ManyToManyField change (I > say "possibly" because I haven't thought around the issue much, so don't > know if ther

Re: 1.2 Proposal: Extra template tags and filters

On Tue, Aug 11, 2009 at 9:50 AM, Richard Davies wrote: > With 1.1 out of the door (great!), here's a thought for 1.2... Actually, it's about six thoughts. I'll give you my quick thoughts below, but if you're serious about discussing this stuff you'll want to have a thread for each of 'em so that

Re: 1.2 Proposal: Extra template tags and filters

On Tue, Aug 11, 2009 at 10:32 AM, Andrey Fedorov wrote: > Sorry, new to the group - is there an easy way to search old threads? Google > keeps pointing me to the docs... It's in the footer that Google adds to every message: > For more options, visit this group at > http://groups.google.com/group

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

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: 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: 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: 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: 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: 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

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: 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

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: 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: 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

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: 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, &

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: 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: 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: 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: 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

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: 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

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?

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: > &

[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: 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] 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:

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] 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!

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.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

[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

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

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: 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: 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: 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: 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: 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: 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

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

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

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

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: 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

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: 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

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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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

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: 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

<    6   7   8   9   10   11   12   13   14   >