Do we add versionadded blocks or does the release manager?

If I'm contributing a new feature, would it be appropriate for my PR to include the `versionadded` block in the documentation (using the current "in-development" version number which as of today is 4.0), or is managing the `versionadded` block something that the release manager does? Thanks in

Re: On adding comments to database schema

te with you on it together. Otherwise I'll give it my best shot. On Thursday, May 6, 2021 at 6:39:45 AM UTC-7 t...@carrick.eu wrote: > It's funny that you bring this up, I was actually looking at this today > and thinking about picking it up next week. > > Jared, the PR wa

Re: On adding comments to database schema

KimSoungRyoul would you like help with writing the docs and tests for this? I'd like to contribute to Django in some way and this is a feature my company would greatly value (we have Data Scientists and DBAs interacting with db tables managed by Django, so having comment documentation at the DB

Re: On adding comments to database schema

KimSoungRyoul it looks like there is feedback on the PR you created (PR #12605 ) and Marius also pointed out that docs and tests are missing. Would you like help with the docs and tests? We've recently added some data scientists and dbas to our team

Minor admin template tweaks

etter if I could leave base.html untouched, and just extend base_site.html. So I added an empty block at that location in base.html. See commit <https://github.com/jaredahern/django/commit/7f6f3c7599d4eff079a970b400588e5b2504317b> . Would either or both of these be acceptable for PRs? Wo

Re: Add Alias or annotations without group-by support?

I have also run into this exact problem. Would love to get this fixed. Have you found a good workaround? On Tuesday, December 26, 2017 at 12:37:16 PM UTC-6, Cristiano Coelho wrote: > > Hello, I'm having a hard time explaining the exact issue but I hope it's > clear enough. > > > Following this i

Re: URLValidator on urls without protocol

Yes it indeed was. That was a mistake on my part. I saw it as soon as I submitted. Sorry. On Nov 17, 2012, at 11:32 PM, Karen Tracey wrote: > On Sun, Nov 18, 2012 at 12:21 AM, Jared Martin wrote: > I don't mean to wake a dead dog, but what has become of this? I came across >

Re: URLValidator on urls without protocol

I don't mean to wake a dead dog, but what has become of this? I came across this problem today. For now, I've subclassed. But it should be fixed, right? On Sunday, June 20, 2010 7:35:23 PM UTC-6, Samus_ wrote: > > ticket: http://code.djangoproject.com/ticket/13804 > > also found a real-life scena

Re: Proposal - ChoiceField.choices need to accept callable, not only list or tuple

I say go for it, and post again with a patch and issue number (once you've created them). Your idea seems sound. Jared On Mon, Mar 22, 2010 at 11:30 PM, George Karpenkov wrote: > Hi, > > The subject pretty much describes all of it. If 'initial' can be a > callable, w

Re: dbsettings, and user configurable app settings

thing in a pythonic manner. Jared On Wed, Mar 10, 2010 at 7:51 AM, Brian Rosner wrote: > > On Mar 10, 2010, at 7:16 AM, Joan Miller wrote: > > > It's a disaster from the maintenance view point. If it were not so, > > then people would not be proposing to refactor

Re: dbsettings, and user configurable app settings

uot;readonly" flag in the settings (if you were using appsettings) and (c) is provided by appsettings out of the box. So it looks like the thing that needs work/thought/design decisions would be (a). Could you give an example use case of that sort of "project installation setting"

Re: Easier debugging of Django templates. {% try %} ... {% endtry %} template tag and traceback.

On a related note, is there a way to tell templates *not* to fail silently? (most tags etc. do) for testing/debugging purposes? jared On Fri, Mar 5, 2010 at 9:53 AM, Jonathan S wrote: > > On Mar 5, 5:49 pm, Jared Forsyth wrote: > > I presume these only get shown with DEBUG turned

Re: Easier debugging of Django templates. {% try %} ... {% endtry %} template tag and traceback.

I presume these only get shown with DEBUG turned on? On Fri, Mar 5, 2010 at 9:09 AM, Jonathan S wrote: > Hi Django users, > > We made at our company, City Live, a template tag you may be > interested in. > It's a try/catch statement. When anything in the try block fails, a > traceback through all

Re: Django documentation for newer users

To be honest I am quicker to just go to django's source code rather than the docs, as often I can find what I need there, and the docs aren't (imo) organized enough to provide much of an advantage. On Fri, Mar 5, 2010 at 8:46 AM, stherrien wrote: > Hi all, > > > I have a request that django docu

Re: 2 small tickets

2/flatpages_admin_trunk.diff>I ended up with). Thanks Jared On Wed, Mar 3, 2010 at 11:24 AM, Karen Tracey wrote: > On Wed, Mar 3, 2010 at 12:33 PM, Jared Forsyth wrote: > >> As a general "best practices" question: When I update a ticket w/ a test >> case and

Re: dbsettings, and user configurable app settings

configuration options which are available to a user who doesn't have server write access. jared On Wed, Mar 3, 2010 at 8:07 PM, orokusaki wrote: > I don't think that settings are for users. They are for the developer. > The type of settings you are looking for really should be set

Re: 2 small tickets

As a general "best practices" question: When I update a ticket w/ a test case and better patch, do I uncheck 'needs better patch' and 'needs testcases'? Or do I leave that to the person who originally checked them? thanks, Jared On Wed, Mar 3, 2010 at 1:08 AM, Ru

2 small tickets

d time for very small bugs w/ a patch attached? for reference, the tickets: http://code.djangoproject.com/ticket/12974, http://code.djangoproject.com/ticket/12972 thanks, Jared -- You received this message because you are subscribed to the Google Groups "Django developers" group. To

Re: dbsettings, and user configurable app settings

store your configuration, but it also gracefully degrades in the absence of a database -- all settings are still accessible, but are read-only. Take a look at the project on github for a better example/docs: http://github.com/jabapyth/django-appsettings <http://github.com/jabapyth/django-appsetti

Re: dbsettings, and user configurable app settings

roving, so I might try to get it polished and more integrated w/ contrib.admin, and see how it works. Jared On Fri, Feb 26, 2010 at 11:00 AM, Wes Winham wrote: > I'd love to see a better way of managing settings in the core of > django. It's a real pain point sometimes for writi

dbsettings, and user configurable app settings

ourage app maintainers to have more settings, thereby making the apps even more portable. Any thoughts? Thanks, Jared -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googleg

Moving the Django Project to a DVCS

Having talked to several people at DjangoCon about this, I would like to start a formal discussion here. It was asked of the Django Core Dev panel, why had the project not yet moved to a distributed version control system? My interpretation of the answer was that there is little incentive for the

Re: #1443: strftime for date and datetime before 1900

Is there any movement on this issue? I'm working on designing a site dealing with historical data and pretty much all of the dates involved are before 1900 (1600-1800). Would be really nice to get a solid solution on this. On Mar 19, 10:45 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On

Re: django-restapi Improvements Proposal

on? Maybe we can get a discussion going there. jared --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To u

Re: django-restapi Improvements Proposal

objects, like this one: class HttpResponseUnauthorized(HttpResponse): status_code = 401 def __init__(self, www_authenticate): HttpResponse.__init__(self) self['WWW-Authenticate'] = www_authenticate This seems to be the style adopted in django.http jared --~--~-~-

Re: django-restapi Improvements Proposal

created another separate source tree. > Anyways, we will study your code and if you agree, we can contribute > in a branch leaded by you. I look forward to hearing your thoughts! jared --~--~-~--~~~---~--~~ You received this message because you are subscribe

django-restapi Improvements Proposal

anyone is interested, please take a look at the rest of the code, I am very curious to get feedback on its design and utility. Thanks! jared --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django develope

Re: Having problems getting django running under apache and mod_python

anger the developers). Many of the developers also monitor the users group, but this group is dedicated to issues concerning the development of django itself. Good luck, jared On Oct 29, 2007, at 1:51 PM, crudolph wrote: > > Hi, > > The project I'm working on works just fine

Re: Documentation restructuring

pared to 15 minutes). Again, this is mostly a database issue, so perhaps somewhat off topic. > What, like Vietnam? > http://blogs.tedneward.com/2006/06/26/The+Vietnam+Of+Computer > +Science.aspx Yes, that's exactly what I meant. I look forward to seeing how much better it can get!

Re: Documentation restructuring

n might want to link outside to a more in depth explanation of the awkwardness of ORM Obviously these aren't very major points, and some of them are more than hinted at already in the documentation, but we all know explicit is better than implicit. Anyhow, keep up the good work. jared --~

Re: Customizable app/project skeletons

The skeleton exists to overwrite the settings.py that is generated so I don't have to modify things like TIME_ZONE, MEDIA_URL, etc, as well as have my extra bits that I like: if getpass.getuser() == 'jared': PROJECT_DIR = '/Users/jared/Desktop/project/'

Customizable app/project skeletons

I have a common set of extra bits that I put in my settings.py files and re-input them each time I create a project. I would like to have a directory like ~/.django_skeletons/project that houses my customized settings.py (and perhaps others). It seems to me this would be a fairly simple undertaki

Re: Proposal: Generic newforms media

On May 26, 10:17 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > I would assume the the mechanism for exposing this would allow it to > be done anywhere in the template, so that CSS/JS could be pulled in as > part of the of the resulting (X)HTML document (in the case of > CSS, to remain valid, i

Re: Proposal: Generic newforms media

This gets a little complicated: tags are only allowed inside tags, otherwise you have invalid (X)HTML. The javascript portion seems fine, however I would see media as a class, not as a method, ala a model's Meta class: class MyWidget(Widget): ... class Media: js = ('/path/to/js'

get_(list|object)_or_404 extension to accept QuerySets -- design decision?

I submitted a patch to extend both get_object_or_404 and get_list_or_404 to accept QuerySets. Current usage: get_object_or_404(Poll, pk=1) get_object_or_404(Poll.my_objects, pk=1) New usage: get_object_or_404(Poll.objects.live(), pk=1) Tests and docs were added to the patch. Does this need a de

Re: get_(list|object)_or_404 extension to accept QuerySets -- design decision?

Forgot the link: http://code.djangoproject.com/ticket/4373 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubs

Re: Login required across entire project Middleware

Joe wrote: > It does bring up the general sort of question - is there a mechanism by > which individuals can get "whitelisted" or otherwise allowed access to > the wiki to post up code, patches, etc? I put some thought into this but couldn't figure out a way to make this feasible. This would almo

Re: Login required across entire project Middleware

I forgot to mention that I attempted to put this in the Wiki again and askimet failed me. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develo

Re: Login required across entire project Middleware

Thanks, Joe. I've actually updated it to this: from django.conf import settings from django.contrib.auth.views import login from django.http import HttpResponseRedirect class RequireLoginMiddleware(object): """ Require Login middleware. If enabled, each Django-powered page will require

Login required across entire project Middleware

I'd like to add a Middleware class that I wrote to the Wiki, but I keep getting rejected by askimet. The class requires an authenticated user for every view. This is beneficial for any closed project. Does anyone suppose something like this is beneficial enough to make it into the Django source?

Re: Akismet is playing up

I haven't been able to submit anything. And I like to think I contribute quality material! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-devel