Re: Django admin, 'Save as new' option, duplicate m2m relations

2013-12-10 Thread Tim Graham
Hi, django-developers is for discussing the development of Django itself, not for answering user queries. If you have a "how do I" question, please direct it to django-users. Thanks! On Tuesday, December 10, 2013 3:57:23 AM UTC-5, Gheorghe Chirica wrote: > > Hi. > > I have a simple model which h

Re: Trac and getting started contributing (was: 1.7 Release Schedule)

2013-12-11 Thread Tim Graham
Hi Christian, I'd recommend leaving comments like that on the ticket itself rather than in this thread. It very well could be that the ticket has been resolved since someone last looked at it. Please go ahead and resolve the ticket if you confirm that to be the case. I'd also suggest starting

Re: python querry on firebug extention .

2014-01-11 Thread Tim Graham
Please don't crosspost to both django-developers and django-users. The topic of this list is the development of Django itself, django-users is for usage questions, although it's not clear to me how this question is related to Django. On Saturday, January 11, 2014 1:18:00 PM UTC-5, JAI PRAKASH S

Re: Is it a mistake on docs for django 1.5?

2014-01-20 Thread Tim Graham
Yes, if you check the 1.6 version of the docs, you'll see it's different. I think if this commit were backported to the 1.5 docs, it would remedy the issue. Can you confirm? https://github.com/django/django/commit/e03a88ba217006fbd7618e3f836c2f6210638aaf On Monday, January 20, 2014 3:35:52 PM U

Re: Quick question re typo-fixing etiquette

2014-01-24 Thread Tim Graham
Any logical grouping like "Fixed bad apostrophes" or "Fixed grammar errors in docs/index.txt" would be acceptable. We definitely don't want a PR for every individual correction as that'll just clutter the commit history. Thanks! On Friday, January 24, 2014 9:21:10 AM UTC-5, gilberto dos santos

Re: #19182 backport request

2014-02-14 Thread Tim Graham
I sympathize with your frustration. On the other hand as we have over 500 bugs in Trac, and I'm not sure starting to accept documentation requests for them is the best use of our resources. I'm not sure the feature is really completely broken enough to warrant removing it from the docs? On Frid

Re: ForeignKey in Inline generates lots of queries

2014-02-21 Thread Tim Graham
Hi John, django-developers is for discussion of the development of Django itself. It isn't a second level support channel if your query on django-users goes unanswered. Thanks! On Thursday, February 20, 2014 5:45:27 PM UTC-5, john@plushrugs.com wrote: > > I posted this to Django users, but

Re: GSOC 2014 Project Proposal

2014-02-23 Thread Tim Graham
As someone who has worked on Django's docs a lot, I've considered pitching in to help update the Django Book. However, I'm not sure it's really the best use of time as there's a lot of overlap between Django's docs and the book. Unless someone wants to argue otherwise, I suggest we adapt any po

Re: GSoC 2014 proposal [Improving error reporting]

2014-02-24 Thread Tim Graham
A starting place for this would be to bring the BetterErrorMessages wiki page up-to-date by removing items that have been fixed or "won't fixed". Then it'll be easier to see what's left and whether or not there is enough to fill 12 weeks. On Monday, February 24, 2014 10:43:04 AM UTC-5, anubhav

Re: GSoC 2014 proposal [Improving error reporting]

2014-02-24 Thread Tim Graham
leted by community members in the meantime. Presumably if your proposal were accepted, you could assign them to yourself at that time. On Monday, February 24, 2014 3:48:49 PM UTC-5, anubhav joshi wrote: > > > > On Monday, February 24, 2014 9:45:30 PM UTC+5:30, Tim Graham wrote: &

Re: GSoC 2014 proposal [Improving error reporting]

2014-02-27 Thread Tim Graham
I think it'll be better to put your analysis of each ticket on the ticket itself. Then when you're finished with that, put together a more high level overview of the analysis you've done. I think it will be easier to give feedback if you structure your thoughts in this way. Thanks! On Thursday,

Re: GSoC 2014 proposal [Improving error reporting]

2014-02-27 Thread Tim Graham
oshi wrote: > > > > On Friday, February 28, 2014 2:03:10 AM UTC+5:30, Tim Graham wrote: >> >> I think it'll be better to put your analysis of each ticket on the ticket >> itself. Then when you're finished with that, put together a more high level >>

Re: Django 1.7: modelformset_factory() vs formset_factory()

2014-03-02 Thread Tim Graham
Yes, see https://code.djangoproject.com/ticket/17642. If you can bring the patch up to date in the next day or two, I'll try to help review and commit it. > On Sunday, March 2, 2014 2:05:56 PM UTC-5, Anders Steinlein wrote: Now that formset_factory() from 1.7 accept num_min and validate_min >

requiring login to perform Trac actions?

2014-03-03 Thread Tim Graham
There's been some discussion on ticket #22067 and #django-dev about requiring Trac login to help cut down on spam and generally improve the quality of the discussion. Claude: I think that forcing registration would be fine. It adds a small barrier

Re: [GSoC 2014 Proposal] Improving Error and Fixing up related issues.

2014-03-10 Thread Tim Graham
Hi Anubhav, It'll be easier to review if you can include ticket numbers with each item in the 2.X sections. e.g. "Unpickling Models and QuerySet from incompatible version. (#X)" Ideally, the ticket number would be linked to Trac. Then I would repeat these summaries & ticket numbers in each

Re: Hi

2014-03-10 Thread Tim Graham
Hi Gent, Have you read the information on our wiki page: https://code.djangoproject.com/wiki/SummerOfCode2014 ? On Monday, March 10, 2014 5:19:54 PM UTC-4, Gent Binaku wrote: > > Hi > I have moderate skills in programming > I have experience in Python > > And i really wanted to be part of the

Re: Different URLCONF for different domains

2014-03-12 Thread Tim Graham
This discussion list is for the development of Django. Questions about how to use Django with your project belong on the django-users mailing list. On Wednesday, March 12, 2014 8:03:54 AM UTC-4, Guy Tamir wrote: > > Hey all, > > I have a Django app that serves to multiple domains. > In the primar

Re: [GSoC 2014 Proposal] Improving Error and Fixing up related issues.

2014-03-27 Thread Tim Graham
As far as I know, we have no plans to request further details from any of our applications. On Thursday, March 27, 2014 5:46:55 AM UTC-4, anubhav joshi wrote: > > I read on google melange: > "mentoring organizations may request further proposal detail from the > student applicant." > > My tests

Deprecating Widget Media class

2014-04-01 Thread Tim Graham
There's been some discussion in ticket #22298about deprecating the widget Media class. If this would make you particularly happy or sad, please leave your feedback on this thread or on the ticket. -- You received this message because you are subscr

Re: condition decorator: if-unmodified-since support and updated etags

2014-04-16 Thread Tim Graham
Hi Thomas, You can read about our contributing process here: https://docs.djangoproject.com/en/dev/internals/contributing/ In particular, there's a section entitled "Submitting patches". Tim On Wednesday, April 16, 2014 9:56:57 AM UTC-4, Thomas Tanner wrote: > > Hello, > I have implemented sup

Re: condition decorator: if-unmodified-since support and updated etags

2014-04-16 Thread Tim Graham
Tanner wrote: > > Hi Tim, > I'm a bit confused by: > > On 16.04.14 16:51, Tim Graham wrote: > > https://docs.djangoproject.com/en/dev/internals/contributing/ > > Requesting features: > First request the feature on the django-developers list, not in the > tic

Re: Data Migrations and Testing

2014-04-21 Thread Tim Graham
I have been thinking that maybe we should delay #22340 (Legacy Table Creation Methods Not Properly Deprecated) until 1.8 so that migrations won't be required until Django 2.0. I'm not sure how feasible it is to remove Django's test suite usage of it in the next week and a half, if we are still

Re: error in "makemessages" command on latest django version (1.8dev)

2014-05-02 Thread Tim Graham
No, a ticket isn't needed since it's already been fixed. Also, since this feature wasn't released, we could have simply reopened the original ticket. On Friday, May 2, 2014 12:58:47 PM UTC-4, Fabio Caritas Barrionuevo da Luz wrote: > > it was really a bug > > > apparently solved in > > https://g

Re: Release of 1.7 news for podcast?

2014-05-18 Thread Tim Graham
You can use this link to see the current list of release blockers for 1.7: https://code.djangoproject.com/query?status=assigned&status=new&version=!master&severity=Release+blocker&col=id&col=summary&col=status&col=owner&col=type&col=component&col=changetime&desc=1&order=changetime I would guessti

Re: #22383 Add the HTML5 required tag to the input fields which are required for database entry

2014-05-19 Thread Tim Graham
Here is a more concrete proposal based on Loic's comment in the ticket: A normal deprecation cycle based on the value of a new ` use_required_attribute` boolean attribute on forms. To deprecate you could do: class form.Form(object): #... use_required_attribute = None class BoundField(

Re: FormWizard needs confirmation step logic. ticket #21644

2014-05-26 Thread Tim Graham
My observation is that not many core developers seem interested in contrib.formtools these days. It was added by Adrian in 2006, but as far as I can see from the commit history, it hasn't received much love lately. If would be a good candidate for deprecation from Django itself, in my opinion.

Re: FormWizard needs confirmation step logic. ticket #21644

2014-05-26 Thread Tim Graham
If we did split it out, would you be interested in being a maintainer? On Monday, May 26, 2014 6:51:13 PM UTC-4, Gordon wrote: > > > > On Monday, May 26, 2014 6:04:31 PM UTC-4, Tim Graham wrote: >> >> My observation is that not many core developers seem interested in &g

Re: SMTP configuration in a dict

2014-05-28 Thread Tim Graham
Ramiro tried to do something similar, moving the cookie settings to a dictionary, see #21051 , but gave up due to backwards compatibility concerns. Not saying it's impossible, but it may be a bit trickier than it looks at first. On Wednesday, May 28,

Re: Make url patterns group kwargs more simple

2014-05-28 Thread Tim Graham
There was also a mention in IRC by a core dev (Jannis, I think) about the possibility of merging http://amitu.com/smarturls/ into core. I agree URL regexes is something that we could improve, but as there are many solutions out there, this would require discussion and a consensus. On Wednesday

Re: shown all active users in template

2014-05-28 Thread Tim Graham
Please ask questions about using Django on the django-users list. The topic of this list is the development of Django itself. p.s. You are unlikely to get much help with the level of detail in your question. On Wednesday, May 28, 2014 2:48:35 PM UTC-4, Ali hallaji wrote: > > Hi, > I write forum

Re: FormWizard needs confirmation step logic. ticket #21644

2014-06-02 Thread Tim Graham
contrib.databrowse is an example of something that was removed from Django. It seems to have found a home here: https://pypi.python.org/pypi/django-databrowse Deprecation of contrib.formtools was actually proposed on the mailing list in 2011, see https://groups.google.com/d/topic/django-develo

Re: Changing development server threads type.

2014-06-04 Thread Tim Graham
I think we should try to move away from maintaining our own web server and focus our efforts on trying to integration with others like gunicorn (#21978 ). On Tuesday, June 3, 2014 12:43:19 AM UTC-4, Moayad Mardini wrote: > > Hi, > > The development se

Re: LOCALE_PATHS should have a check to make sure it's a list/tuple

2014-06-06 Thread Tim Graham
Sure, patches welcome. `django.conf.__init__` already has some "tuple_settings" logic which is looks like would probably work for this. On Friday, June 6, 2014 11:51:30 AM UTC-4, Tim Shaffer wrote: > > I'm playing around with 1.7b4 and I was trying to track down why my app > was not auto-reloadi

Re: Offline Appcache/Reponse Headers

2014-06-13 Thread Tim Graham
Please use django-users for usage questions (although it's not clear your question is about Django and not Firefox). This list is for the discussion of the development of Django itself. On Friday, June 13, 2014 9:34:57 AM UTC-4, Max wrote: > > Hi there, > > I am trying to build an offline-django

Time to drop support for Oracle < 11?

2014-06-13 Thread Tim Graham
Hi Shai and Oracle users, I came across a ticket (#11580 ) which proposes a fix that works on Oracle > 11 but not for older versions along with the suggestion: "Perhaps it makes sense to abandon support for Oracle versions below 11g in Django 1.6 or

Re: Time to drop support for Oracle < 11?

2014-06-14 Thread Tim Graham
te: > > Hi Tim and all, > > > > On Saturday 14 June 2014 03:52:57 Tim Graham wrote: > >> > >> Release - GA Date - Premier Support Ends - Extended Support Ends > >> > >> 11.1 - Aug 2007 - Aug 2012 - Aug 2015 > >> 10.2 - Jul 2005

Re: Ready for checkin

2014-06-16 Thread Tim Graham
+1 to "check-in" On Monday, June 16, 2014 12:08:43 PM UTC-4, Daniele Procida wrote: > > "Ready For Check-in" appears in the docs once; "Ready for Checkin" appears > five times, and on Trac. > > Can we change it universally to "Ready for check-in"? Or better "Ready for > core team review"? > >

Re: [GSOC] model/options.py test suite released

2014-06-17 Thread Tim Graham
Hi Daniel, I took a quick look and left a couple comments on the pull request: https://github.com/django/django/pull/2823 On Tuesday, June 17, 2014 7:35:55 AM UTC-4, Daniel Pyrathon wrote: > > Hi All, > > I have opened a Pull Request for a unit test suite for the current > implementation of mode

Re: Migrations and Reusable Apps

2014-06-17 Thread Tim Graham
I'm sure Andrew will have more info, but you could use MIGRATION_MODULES and generate migrations for any 3rd party apps that don't have them. I'm not sure how the transition when the app starts shipping its own migrations will go. On Tuesday, June 17, 2014 9:18:57 AM UTC-4, Mark Lavin wrote: >

Re: Strange behavior when running simple query via script versus view code

2014-06-17 Thread Tim Graham
Please use django-users for usage questions. This list is for the discussion of the development of Django itself. On Tuesday, June 17, 2014 7:41:04 PM UTC-4, Jason Skicewicz wrote: > > I have a many to many relationship from my UserProfile object to an object > called ThemeTimes. The declaratio

Re: django-firebird backend: migrations and NULL fields

2014-06-19 Thread Tim Graham
Backported in 30d8b95139a1fa3070f3b112115e624ffcf8e555, thanks for the reminder. On Thursday, June 19, 2014 9:36:54 AM UTC-4, Maximiliano Robaina wrote: > > > El martes, 20 de mayo de 2014 09:27:48 UTC-3, Andrew Godwin escribió: >> >> Yes, I'm aware add_field is also in need of expansion points -

Re: Unexpected behavior in admin views for _popup=1

2014-06-26 Thread Tim Graham
The Django admin doesn't generate links to render the change or delete pages in pop-ups which is the reason this functionality wasn't implemented. While it seems like a reasonable request, I'm hesitant to add support for them because if such pages aren't in the normal admin workflow they will p

Re: Regression in ValidationError in 1.7

2014-06-27 Thread Tim Graham
Russ, could you include a code snippet of what no longer works? I think there is a documented solution that involves modifying Form._errors (see https://docs.djangoproject.com/en/1.6/ref/forms/validation/#django.forms.Form.clean), but I'm not sure if you're doing that or something different. Th

Re: APPEND_SLASH only 500's for POST, not for PUT/DELETE. Intentional?

2014-06-27 Thread Tim Graham
No, I don't think it's intentional -- more that Django wasn't initially built with REST APIs in mind. On Friday, June 27, 2014 2:13:10 PM UTC-4, Phill Tornroth wrote: > > Ran into this recently and it seemed counterintuitive. The APPEND_SLASH > functionality 500's for POST, but returns a 302 for

Re: APPEND_SLASH only 500's for POST, not for PUT/DELETE. Intentional?

2014-06-27 Thread Tim Graham
We're talking about the check in CommonMiddleware right? Since it's done only if DEBUG is True, it seems to serve mostly as a courtesy to alert developers of the inability of redirects being able to preserve POST data. Thinking about it a bit more, as far as I know, DELETE requests don't typica

Re: collectstatic - override default ignore list

2014-07-01 Thread Tim Graham
Jannis commented on the ticket, "This is simple, don't add a global setting but a parameter to the staticfiles app config. That's where such things belong now." This makes sense to me. I suppose we should look into whether it makes sense to move at least some of the other static files settings

Re: modelformset_factory and unique_together don't always validate unique fields

2014-07-03 Thread Tim Graham
Another suggestion: could you include the field on the form but use a HiddenInput widget? On Thursday, July 3, 2014 9:03:25 AM UTC-4, Jon Dufresne wrote: > > On Thu, Jul 3, 2014 at 1:12 AM, Florian Apolloner > wrote: > > To me this is no shortfall but expected and good behaviour, including > o

Re: FR: Setting for CSRF Header (pull-request included)

2014-07-08 Thread Tim Graham
The main problem I see with this approach is that it would no longer be straightforward for 3rd party code to access these settings. You'd need something akin to get_user_model() to retrieve the currently installed CSRF middleware so you could access its settings. Take a look here for examples

Re: Decision for ticket #14787

2014-07-10 Thread Tim Graham
It could be useful, however, I think many projects would also want to have some way of configuring the max file upload size without having to specify it on every FileField. One way to achieve this might be if a a custom file upload handler could raise an exception that would be presented as a fo

1.7 release status (RC2 coming soon)

2014-07-10 Thread Tim Graham
It's been 2 weeks since the release of 1.7 RC1 and we've seen several bugs opened and fixed, with several still open [1]. We plan to issue a second RC sometime next week if we can empty that list. Help us fix the issues if you have some time and keep testing! [1] https://code.djangoproject.com

Removing formtools from contrib (and call for maintainers)

2014-07-11 Thread Tim Graham
continuing https://groups.google.com/d/topic/django-developers/km2xIHM-gIA/discussion under a better subject (was "FormWizard needs confirmation step logic. ticket #21644")... I'd like propose removing formtools from contrib. Reason to move it out: - Allow more maintainers next to Django core

deprecate contrib.webdesign? (#22789)

2014-07-11 Thread Tim Graham
It provides the lorem template tag. The functionality has not changed in 7 years and it has 20 commits in its history which are mostly maintenance oriented (pep8, adding app loading compatibility). Options: * Move it into the main template tag library and deprecate the hook in contrib. * Re

future of @skipIfCustomUser decorator? (#22993)

2014-07-11 Thread Tim Graham
With the test discovery changes in 1.6, the tests for django.contrib apps are no longer run as part of a user's project. For this reason I believe we no longer need to decorate tests in contrib.auth, formtools, and flatpages with @skipIfCustomUser. Is that correct? If so, should we keep the dec

Re: deprecate contrib.webdesign? (#22789)

2014-07-12 Thread Tim Graham
Okay, then I'm in favor of moving it to built-in tags as Aymeric suggested. On Friday, July 11, 2014 6:57:51 PM UTC-4, Russell Keith-Magee wrote: > > > On Fri, Jul 11, 2014 at 11:40 PM, Daniele Procida > wrote: > >> On Fri, Jul 11, 2014, Tim Graham > >>

Re: future of @skipIfCustomUser decorator? (#22993)

2014-07-12 Thread Tim Graham
Okay, the only real maintenance burden I'm concerned about is figuring out if new tests in Django's test suite need to use the decorator or not. Maybe we could consider dropping that requirement by Django 2.0 or so. On Friday, July 11, 2014 8:27:22 PM UTC-4, Michael Manfre wrote: > > > > > On Fr

Re: Removing formtools from contrib (and call for maintainers)

2014-07-12 Thread Tim Graham
r a year but I'm more than happy to use a >> non-updated package in core. >> >> Josh >> >> On Saturday, 12 July 2014 09:25:48 UTC+10, Russell Keith-Magee wrote: >> >>> >>> On Fri, Jul 11, 2014 at 10:52 PM, Tim Graham wrote: >>&

Re: Removing formtools from contrib (and call for maintainers)

2014-07-15 Thread Tim Graham
ice for the app authors, which >> is also the reason why it has some incomplete data about app features (the >> “grids”). >> >> Jannis >> >> >> On 12.07.2014, at 01:25, Russell Keith-Magee >> wrote: >> >> > >> > On Fri, J

Re: Updating the organization of the Django Project

2014-07-23 Thread Tim Graham
+1. It might be better to move the more temporal information (team.txt and roles.txt) to a protected wiki page (or something similar) so there's one canonical place to view and update that information (rather than the documentation which has a branch for each release of Django). On Wednesday,

Re: send clickable email

2014-07-24 Thread Tim Graham
You'll get answers to your questions on the django-users email list. The list you've posted to is django-developers, an email list for the discussion of the development of Django itself. You might also find helpful the #django IRC channel on irc.freenode.net. On Thursday, July 24, 2014 5:26:

Re: 1.7 release status (RC2 coming soon)

2014-07-24 Thread Tim Graham
kers." Opinions from the community on that would be welcome. On Thursday, July 10, 2014 5:49:10 PM UTC-4, Tim Graham wrote: > > It's been 2 weeks since the release of 1.7 RC1 and we've seen several bugs > opened and fixed, with several still open [1]. We plan to issue

Re: 1.7 release status (RC2 coming soon)

2014-07-25 Thread Tim Graham
Here is the ticket for putting pre-releases on PyPI. https://code.djangoproject.com/ticket/21108 We tried it for 1.7 alpha but it didn't work. On Friday, July 25, 2014 11:21:21 AM UTC-4, Carl Meyer wrote: > > On 07/25/2014 09:17 AM, Ryan Hiebert wrote: > > On a somewhat-related tangent, I seem

Re: SchemaEditor + DatabaseConnection

2014-07-27 Thread Tim Graham
l, > > I'm working on https://code.djangoproject.com/ticket/56 for the > EuroPython sprint. There was a PR for it ( > https://github.com/django/django/pull/1156) but it was rejected by Tim > Graham because the code should apparently be in the SchemaEditor instead of > the Dat

Re: Pull django-registration into contrib?

2014-08-01 Thread Tim Graham
If no one has volunteered to maintain it in nearly a year since James stepped down, I think you'll have a tough time convincing us it's important enough to move into contrib. Also, the recent trend has been to remove things from contrib (comments, localflavor, formtools soon). django-registrati

Re: Pull django-registration into contrib?

2014-08-01 Thread Tim Graham
unt of technology dev, design > and decision experience, I'd say having proper users and authentication > makes for a big, fairly rare distinguishing feature, and reliable > registration capabilities are an important complement to that. > > > On Friday, 1 August 2014 13:25:25 UTC+2,

Re: Updating the organization of the Django Project

2014-08-01 Thread Tim Graham
Christian, have you seen the patch review checklist I put together? https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/submitting-patches/#patch-review-checklist That is basically what I do when I review a patch. If a patch meets those guidelines, please mark it RFC. A co

Re: Pull django-registration into contrib?

2014-08-02 Thread Tim Graham
On a related note, djangoproject.com depends on django-registration so we need to update it for 1.7 compatibility or remove the dependency. On Friday, August 1, 2014 6:13:34 PM UTC-4, James Bennett wrote: > > Speaking for myself, I am still willing to hand over the reins of > django-registration

Re: FR: Setting for CSRF Header (pull-request included)

2014-08-04 Thread Tim Graham
Did you look at the github code search link on my previous email? You may substitute the other CSRF setting names and determine if you think people are doing legitimate things or not. On Monday, August 4, 2014 5:13:57 PM UTC-4, Wes Alvaro wrote: > > Yeah, I would agree with you. You should know

Re: Proposal: Password Validity Layer

2014-08-05 Thread Tim Graham
In fact, there is an accepted ticket: https://code.djangoproject.com/ticket/16860 It may be better to try out the "AppConfig setting" route as discussed in https://groups.google.com/d/topic/django-developers/qnnCLppwA3o/discussion rather than adding a new top level setting. Perhaps you can try

Re: Requiring GitHub login for actions on Trac

2014-08-06 Thread Tim Graham
I proposed the idea a couple months ago and got several +1's. The main concern was from Shai, "not quite -1, but a strong -0 on "blessing" any single oAuth provider. GitHub is fine, but so are Google, StackExchange, and even the Evil Empires(TM)." https://groups.google.com/d/msg/django-develope

Re: [Discussion] Legacy documentation / Boken docs Django v1.2

2014-08-07 Thread Tim Graham
I'm in favor of discontinuing older version of the docs. I recently fixed the 1.3 documentation builder since there were several complaints, but no one has complained about 1.2. On Thursday, August 7, 2014 7:32:25 AM UTC-4, Areski Belaid wrote: > > Hi Folks, > > I wanted to open a discussion reg

Re: Proposal: Password Validity Layer

2014-08-07 Thread Tim Graham
The custom user idea did seem like a good one to me. I don't think you'd have to rewrite much (anything?) if the only change in your custom user is to add a validate_password() function. If you'd like code up a proof of concept we can take a look. I don't think front-end integration is necessa

Re: ORM Optimization for filtering by related existence

2014-08-07 Thread Tim Graham
Does .filter(somefield__isnull=False) not work for what you're trying to do? On Thursday, August 7, 2014 7:43:07 PM UTC-4, David Butler wrote: > > It would be nice if there was some database level optimization for getting > objects that have related objects that exist. > > This is a slow filter:

Re: The unordered_list template filter suports a format that was seen as old 7 years ago

2014-08-08 Thread Tim Graham
Feel free to submit a ticket and patch that does so. On Friday, August 8, 2014 8:49:47 AM UTC-4, Jaap Roes wrote: > > First link is wrong, was missing a zero > https://code.djangoproject.com/ticket/23260 >

Re: Problem with profile picture and mysql. URGENT !!

2014-08-08 Thread Tim Graham
This mailing list is for the development of Django. Please direct questions about how to use Django to the django-users mailing list. On Friday, August 8, 2014 12:41:52 AM UTC-4, Swathi Rajanna wrote: > > My app does not use South as it keeps giving me django.core.management > Improperly Configu

Re: The unordered_list template filter suports a format that was seen as old 7 years ago

2014-08-08 Thread Tim Graham
tion in the > documentation or should there be some sort of deprecation period? Not sure > what the policy of Django on this sort of thing is. > > On Friday, August 8, 2014 4:13:38 PM UTC+2, Tim Graham wrote: >> >> Feel free to submit a ticket and patch that does so. >

Re: [RFC] Python 3 and MySQL

2014-08-12 Thread Tim Graham
I'd like see some community consensus on the best solution for a MySQL adapter rather than than have more than one build for MySQL. I don't know the MySQL ecosystem very well. Naoki, is there no interest from MySQLdb in your Python 3 compatibility changes? On the PyPI page it says, "Python-3.0

Re: Should exceptions in dev server appear as tracebacks in the console by default?

2014-08-12 Thread Tim Graham
rms.py, models.py etc the only obvious way i >> can think of not going through a request would be a management command? >> >> 2/ wouldn't it be better if, when DEBUG=True, more logging stuff ended up >> in the console? logging for management commands going to

Re: Should AdminSite be able to handle different namespace?

2014-08-13 Thread Tim Graham
I looked into this today and couldn't see why you'd want to have a different `app_name`. In fact doing so would conflict with the docs: "Every instance of a single application will have the same application namespace. For example, Django’s admin application has the somewhat predictable applicat

Re: Master/slave trolling pull request accepted to django master branch

2014-08-14 Thread Tim Graham
This topic is closed and no replies will be tolerated. There are plenty of Trac tickets that could use attention. Thank-you! On Thursday, August 14, 2014 12:56:01 PM UTC-4, Andre Terra wrote: > > That is one great suggestion. +1 and as long as nobody -1s it, we're good > to go! > On Aug 12, 2014

Re: Should AdminSite be able to handle different namespace?

2014-08-22 Thread Tim Graham
topic confusing before I worked on this). On Wednesday, August 13, 2014 3:33:33 PM UTC-4, Tim Graham wrote: > > I looked into this today and couldn't see why you'd want to have a > different `app_name`. In fact doing so would conflict with the docs: "Every > instance of a

integrating django-secure

2014-08-27 Thread Tim Graham
I've started tackling one of the ideas that's been on our GSoC ideas page for a couple years now: integrating django-secure. I chatted with Carl about the idea and he's onboard. There are a couple of design decisions we'll need to make. 1. How to integrate django-secure with the checks framework d

Re: integrating django-secure

2014-08-27 Thread Tim Graham
> outsiders] is a bad look for Django, and certainly doesn't fit with the > "Secure by default" philosophy. > > -- > Curtis > > > On 28 August 2014 10:34, Russell Keith-Magee > wrote: > >> Hi Tim, >> >> On Thu, Aug 28, 2014 at 3:35 AM, Ti

Re: integrating django-secure

2014-08-28 Thread Tim Graham
The settings for the SecurityMiddleware as they appear in django-secure are: SECURE_HSTS_SECONDS=0 SECURE_HSTS_INCLUDE_SUBDOMAINS=False SECURE_CONTENT_TYPE_NOSNIFF=False SECURE_BROWSER_XSS_FILTER=False SECURE_SSL_REDIRECT=False SECURE_SSL_HOST=None SECURE_REDIRECT_EXEMPT=[] Yo-Yo, would be helpfu

Re: integrating django-secure

2014-08-28 Thread Tim Graham
gle dictionary setting called something like SECURITY_MIDDLEWARE_CONFIG? On Thursday, August 28, 2014 6:27:40 AM UTC-4, Tim Graham wrote: > > The settings for the SecurityMiddleware as they appear in django-secure > are: > > SECURE_HSTS_SECONDS=0 > SECURE_HSTS_INCLUDE_SUBD

Re: integrating django-secure

2014-08-28 Thread Tim Graham
as easily be combined in SecurityMiddleware (as it was in django-secure). Splitting it up would require adding more checks (one for each miiddleware) which I wouldn't be wild about. On Thursday, August 28, 2014 6:37:03 PM UTC-4, Carl Meyer wrote: > > On 08/28/2014 06:44 AM, Tim Graham wrote:

Re: integrating django-secure

2014-08-30 Thread Tim Graham
The merging is between the final user settings and global_settings. The advantage is not having to redeclare all the keys in a setting like: SECURITY_MIDDLEWARE = { 'HSTS_SECONDS': 0, 'HSTS_INCLUDE_SUBDOMAINS': False, 'CONTENT_TYPE_NOSNIFF': False, 'BROWSER_XSS_FILTER': False,

Re: integrating django-secure

2014-08-30 Thread Tim Graham
The way the discussion has gone, I think I favor individual settings over settings grouped in a dictionary in this case. If we drop magical merging of dictionary settings (which seems like it will cause more confusion), a user's options for customizing a single key in settings are: 1. Redefine

Re: manage.py migrate doesn't call createsuperuser

2014-08-31 Thread Tim Graham
See #22770 for the ticket. It's also in the migrate documentation. On Sunday, August 31, 2014 11:34:55 AM UTC-4, Shai Berger wrote: > > This was a deliberate

Re: Please don't kill the ecosystem

2014-09-01 Thread Tim Graham
Pkl, if you're interested, I'd encourage you to be more involved in the development process including this mailing list when changes are proposed. I'm afraid raising a whole bunch of old issues that have already been discussed and decided isn't that helpful. Our deprecation policy (as you proba

Re: integrating django-secure

2014-09-03 Thread Tim Graham
Over the past couple days, I've made some more updates and polish to the PR. A couple people have looked at it, but some more eyes would be appreciated as it's hopefully now in a mergeable state. Thanks! https://github.com/django/django/pull/3128 p.s. It uses flat, non-dict settings. We can con

proposing max line length of 119 + enforcing it with flake8

2014-09-03 Thread Tim Graham
Ticket #23395 raised the issue that our contributing guidelines is not exactly clear regarding long lines. Currently it says, "One big exception to PEP 8 is our preference of longer line lengths. We’re well into the 21st Century, and we have high-re

Re: DatabaseError: no such table: django_content_type

2014-09-03 Thread Tim Graham
This is django-developers, the list for discussing the development of Django itself. For questions about using Django, please use the django-users mailing list. It's also helpful to include a traceback of the error. On Wednesday, September 3, 2014 4:29:52 PM UTC-4, Leandro Moreno wrote: > > Hel

Re: Setting dictionaries (was Re: integrating django-secure)

2014-09-05 Thread Tim Graham
In the meantime, shall we abandon the idea of organizing settings in dictionaries for "purity"? May we add new settings as described here: https://code.djangoproject.com/ticket/22734#comment:22 On Friday, September 5, 2014 12:39:02 PM UTC-4, Russell Keith-Magee wrote: > > > > On Thu, Sep 4, 2014

Re: The greatest proposal yet: rename this damn group

2014-09-05 Thread Tim Graham
Russ, I think the suggestion was merely to change the display name of the group. I don't see any downsides to trying something like "Django developers (core development)". On Friday, September 5, 2014 1:45:58 PM UTC-4, Russell Keith-Magee wrote: > > > Hi Robert, > > Thanks for the suggestion. >

Re: Bug in django\forms\models.py in _construct_form, line 593?

2014-09-06 Thread Tim Graham
Hi Piotr, What you've provided is a bit short on details for us to tell. Have you tried searching Trac for a similar issue? "Is this a bug?" questions should usually be asked on the django-users mailing list. A minimal project we can use to reproduce the error is really helpful. If you think it

Re: [RFC] Python 3 and MySQL

2014-09-08 Thread Tim Graham
I'll test mysqlclient-python on my staging CI server today. On Monday, September 8, 2014 3:08:41 AM UTC-4, Claude Paroz wrote: > > Le lundi 8 septembre 2014 08:33:39 UTC+2, Naoki INADA a écrit : >> >> >> On Monday, September 8, 2014 2:04:26 PM UTC+9, Naoki INADA wrote: >>> >>> > >>> > Naoki, >>>

Re: [RFC] Python 3 and MySQL

2014-09-08 Thread Tim Graham
We'd need mysqlclient to support Python 3.2 (or drop official support for MySQL/Python 3.2): django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb module: /var/lib/jenkins/workspace/django-selenium/database/mysql/python/python3.2/tests/.env/lib/python3.2/site-packages/_mysql.cpython

Re: [RFC] Python 3 and MySQL

2014-09-08 Thread Tim Graham
I don't think it'd be a problem, but I don't use MySQL or Python 3.2 on a regular basis. On Monday, September 8, 2014 11:19:56 AM UTC-4, Naoki INADA wrote: > > On Mon, Sep 8, 2014 at 11:28 PM, Tim Graham > wrote: > > We'd need mysqlclient to support Python 3

Re: [RFC] Python 3 and MySQL

2014-09-09 Thread Tim Graham
ttps://github.com/PyMySQL/mysqlclient-python/blob/master/_mysql.c#L150 >>>> https://github.com/farcepest/MySQLdb1/blob/master/_mysql.c#L180 >>>> >>>> I'll investigate the problem, but I can't promise any date for fixing >>>> it. >>>> >

Re: Django 1.7 migrations and third-party imports

2014-09-09 Thread Tim Graham
Questions related to design decisions are a valid topic for django-developers. In this case, please see this documentation: https://docs.djangoproject.com/en/dev/topics/migrations/#historical-models Perhaps Andrew may want to explain the design decision further. On Tuesday, September 9, 2014 5

<    2   3   4   5   6   7   8   9   10   11   >