[ANNOUNCE] Django bug fix releases issued: 1.7.4 and 1.4.19

Today the Django project has issued bugfix releases in the 1.7 and 1.4 release series. Full details are available on the Django project weblog: https://www.djangoproject.com/weblog/2015/jan/27/bugfix-releases-issued/ -- You received this message because you are subscribed to the Google Groups

Re: GSOC 2015 project ideas suggestion

I've created a wiki page for this year. It includes some ideas from past years which may or may not still be relevant (I did some light editing). Of course, you are welcome to propose something entirely different related to your interests. https://code.djangoproject.com/wiki/SummerOfCode2015 O

Re: Pull request builder now on Ubuntu 14.04

gt; > Why don't they build on 14.04? We regularly run Django on EC2 VMs with > 14.04 as the base AMI. > > > > On Monday, January 26, 2015 at 11:33:11 AM UTC-6, Tim Graham wrote: >> >> The pull request builders are now running on Ubuntu 14.04. The master >> stil

importing threading and dummy_threading

As far back as Django 1.4 (didn't check earlier), we use both these patterns in the code: import threading try: import threading except ImportError: import dummy_threading as threading We also have logic in tests to skip if threading isn't available, however, I can't believe that Djang

Re: importing threading and dummy_threading

Here's a 9 year old ticket referencing freebsd5.1... https://code.djangoproject.com/ticket/2052 On Wednesday, January 28, 2015 at 8:51:16 AM UTC-5, Tim Graham wrote: > > As far back as Django 1.4 (didn't check earlier), we use both these > patterns in the code: > >

Re: importing threading and dummy_threading

On Wednesday, January 28, 2015 at 9:37:52 AM UTC-5, Marc Tamlyn wrote: > > Given that it already doesn't worth without full threading in the previous > LTS, I don't think we need to worry about it. > > On 28 January 2015 at 14:32, Tim Graham > > wrote: > >>

automated import sorting and better pull request checks

As a code reviewer, I've really appreciated that we've cleaned up the code using flake8 and have automated "enforcement" via the CI server. I'd like to extend the idea to apply to standardizing import ordering using isort [1]. This mail is to advise everyone of the change and to address any con

Re: automated import sorting and better pull request checks

dea. There are so many changes on PR 4009 that I couldn't check if > you wrote a .isort.cfg. Did you, or are you just using the defaults? > > -- > Aymeric. > > 2015-01-29 14:18 GMT+01:00 Tim Graham >: > >> As a code reviewer, I've really appreciated that

Re: GSOC 2015 project ideas suggestion

The description of that project needs to be updated as I don't think it accurately reflects a direction we want to go. A goal might be the ability to use django.forms without the rest of Django, but there's no need to break django.forms into a separate repository to make this possible. In fact

Re: Updating contributing documentation

Hi Riccardo, Thanks for the feedback. Maybe adding a link to the patch review checklist [1] to the contributing tutorial would be sufficient. Most of the points you've covered are valid and are covered in the rest of the contributing docs. I'd like not to duplicate information if possible, but

Re: status of 1.8 release blockers

=assigned&status=new&keywords=~1.8-beta&col=id&col=summary&col=status&col=owner&col=type&col=component&col=changetime&desc=1&order=changetime I'll follow up next week to ensure we have owners for any issues that remain after the weekend. On Thursday

Re: Usage of field cardinality flags in database schema backends

Seems to me it would be useful to work with some external projects (like taggit) to convert their projects to use only public APIs -- otherwise we are stumbling around in the dark trying to figure out theoretical use cases. On Monday, February 2, 2015 at 5:41:06 AM UTC-5, Anssi Kääriäinen wrote:

Re: automated import sorting and better pull request checks

give it a try on personal project. >> It considers only the global import of the file (I mean on the >> very top on my files and not in the methods / functions). Which >> is exactly what it should do from my point of view. >> >> >> On 01/29/2015 02:18 PM, Tim Graham

Re: automated import sorting and better pull request checks

iting-code/coding-style/#imports Hopefully this allows contributors to more easily handle these fixes on their own in advance of a review from a human! On Thursday, February 5, 2015 at 8:55:06 AM UTC-5, Tim Graham wrote: > > Two new builders run on all pull requests: > >- ​flake8 &l

Re: Getting started : Contributing to Django

A good place to start is reading the contributing documentation: https://docs.djangoproject.com/en/dev/internals/contributing/ The next step is to find a ticket in the area you are interested in and then either: 1) review the existing patch if there is one, 2) improve an existing patch if it has

Re: Elimination of limitations of bulk_create in Django

Please use this mailing list to communicate your ideas and questions regarding GSoC. As I wrote in another thread, "Your odds of acceptance are greatly enhanced if you have a track record of producing good patches (and it will also help you write a better proposal, I think)." On Saturday, Febr

discontinue shipping tests with contrib apps?

I wonder if there is any need to continue to ship tests as part of contrib apps? Currently the contributing docs say, "Tests for contrib apps go in their respective directories under django/contrib, in a tests.py file. You can split the tests over multiple modules by using a tests directory in t

Re: discontinue shipping tests with contrib apps?

Is it a best practice? In my unscientific sampling, none of the following ship tests inside the application directory, but rather in a separate "tests" directory. Or did I misunderstand what you meant? - Django REST framework - django-nap - the apps that split out from contrib (formtools, commen

Re: discontinue shipping tests with contrib apps?

PR is ready for review: https://github.com/django/django/pull/4106 On Tuesday, February 10, 2015 at 12:00:13 PM UTC-5, Carl Meyer wrote: > > On 02/10/2015 12:08 AM, Jannis Leidel wrote: > >> On 10 Feb 2015, at 00:12, Tim Graham > > wrote: > >> > >> Is

Re: discontinue shipping tests with contrib apps?

I don't have a strong opinion on a nested structure for the tests; I merely followed the existing convention for contrib tests that were already in tests/. Note that if we do nest, we still need the "_tests" suffix (or some distinction so to prevent duplicate app_labels from the contrib apps th

Re: status of 1.8 release blockers

mary&col=status&col=owner&col=type&col=component&col=changetime&desc=1&order=changetime On Wednesday, February 4, 2015 at 9:45:33 AM UTC-5, Tim Graham wrote: > > Reminder that the 1.8 beta release is scheduled for twelve days from now: > Monday, February 16.

1.8 bug fix sprinting this weekend

If you would like to contribute to the timely release of 1.8 and if you have some free time over the next couple days, please consider working on something from this list (whether it is writing a patch, reviewing an existing patch, or triaging an issue): https://code.djangoproject.com/query?sta

Re: 1.8 bug fix sprinting this weekend

patches then? > > > > On Thursday, February 12, 2015 at 8:07:46 PM UTC-6, Tim Graham wrote: >> >> If you would like to contribute to the timely release of 1.8 and if you >> have some free time over the next couple days, please consider working on >> somethin

Re: Psycopg2 version support

Unless any counter arguments are presented, I suggest let's require psycopg 2.5 for now. Is there a scenario where you could pip install Django but not pip install psycopg2? On Saturday, February 14, 2015 at 5:43:32 PM UTC-5, Shai Berger wrote: > > Hi all, > > On Saturday 14 February 2015 22:53

Re: Psycopg2 version support

does >>>> not >>>> >>>> Installing psycopg2 2.0.0 requires exactly the same `postgres-*-dev` >>>> libraries that 2.5 does as far as I know. If it is possible to install >>>> psycopg2 via the OS package manager then 2.5 can be installed v

Re: status of 1.8 release blockers

1.8 beta I ask everybody to take a look > and try it out on their projects. Especially if 1.8 alpha 1 didn't work for > you. > > Thanks > > /Markus > > On Saturday, December 20, 2014 at 8:40:33 PM UTC+1, Tim Graham wrote: >> >> As we approach the d

Re: Psycopg2 version support

things. So then the minimum version would be either 2.5; or > 2.4.5 and write special cases in contrib.postgres to deal with that. > > Regards, Wim > > On Monday, 16 February 2015 16:04:50 UTC+1, Tim Graham wrote: >> >> How about this plan: >> * Document 2

Re: status of 1.8 release blockers

ood to me; Markus to review & commit tomorrow. On Monday, February 16, 2015 at 11:12:46 AM UTC-5, Tim Graham wrote: > > There are still quite a few unresolved issues, so the beta release won't > happen today. I'll send an update at the end of the day with the status of &g

Re: Signature of the allow_migrate database router.

I'm not a big user of multi-db so I could be wrong here, but it seems like this API seems to assume that all models in a given app are stored in the same database. Have you thought through what happens if this isn't true? This question seems to come into play when we allowed model=None in RunPy

Re: status of 1.8 release blockers

y can get around the issue by adding `objects = models.Manager()` to > that model. > > Tim, Russ, thoughts 'bout that? > > /Markus > > On Tuesday, February 17, 2015 at 1:05:37 AM UTC+1, Tim Graham wrote: >> >> Here's the status on blockers. Given the work

Re: status of 1.8 release blockers

delaying the beta I think, I'm > getting the feeling you guys are busy enough as it is. > > Op dinsdag 17 februari 2015 18:20:22 UTC+1 schreef Tim Graham: >> >> If it's the only release blocker left and the fix is difficult, I think >> we could issue a beta rele

Re: status of 1.8 release blockers

3 issues remain. I haven't confirmed with the owners, but it seems to me there may be a good chance to wrap them up tomorrow. #24351 RunPython/RunSQL operations in contrib migrations and multi-db routers.

Re: status of 1.8 release blockers

reaks inline admins <https://code.djangoproject.com/ticket/24377> On Thursday, February 19, 2015 at 2:45:07 AM UTC-5, Loïc Bistuer wrote: > > From my point of view #24351 is ready for a final sanity check and > merging. > > -- > Loïc > > > On Feb 19, 2015, at 10:10,

Re: Should the test suite pass on a read-only filesystem?

Sounds good to me. On Jenkins, I think using chmod to remove write permissions from the relevant checkout directories might work. On Saturday, February 21, 2015 at 6:08:38 AM UTC-5, Aymeric Augustin wrote: > > Hello, > > Would it be a good property of the test suite to pass on a read-only > che

Re: status of 1.8 release blockers

7> UUIDField as primary key breaks inline admins <https://code.djangoproject.com/ticket/24377> On Friday, February 20, 2015 at 4:48:01 PM UTC-5, Tim Graham wrote: > > The three issues from last time are resolved, but there is a new issue > I've been working on today. I have a

Re: status of 1.8 release blockers

angoproject.com/ticket/24395> Cannot reference FK relation from inline ModelForm.save() <https://code.djangoproject.com/ticket/24395> There is a chance to resolve them both tomorrow and then release the beta. On Saturday, February 21, 2015 at 3:53:51 PM UTC-5, Tim Graham wrote: > >

Re: Interested in GSoC idea "Replace Form Media Class"

Hi Varun, Thanks for your interest. If you want feedback, you'll need to describe your ideas in more detail. Tim On Monday, February 23, 2015 at 10:31:34 PM UTC-5, Varun Sharma wrote: > > Hi everyone, > > I've been pondering over the django codebase and GSoC ideas for some time > now. I find t

Re: status of 1.8 release blockers

Zero blockers as of this writing. If we survive the next 12 hours with no new ones, I'll release the beta around then (famous last words). On Monday, February 23, 2015 at 7:29:09 PM UTC-5, Tim Graham wrote: > > Previous two issues have been fixed, and now we have two new issues:

[ANNOUNCE] Django 1.8 beta 1 and 1.7.5 released

In addition to a bug fix release for the 1.7 series, the Django team has made the second release on the way to Django 1.8. Check out the blog post: https://www.djangoproject.com/weblog/2015/feb/25/releases/ -- You received this message because you are subscribed to the Google Groups "Django de

Re: User.username max_length 254

Well, this change wouldn't have been made after alpha (feature-freeze) either. As there haven't been any outright rejections of the idea, I think the next step is for someone to write a patch and carefully consider and document and backwards compatibility concerns. On Wednesday, February 25, 20

Re: Extending the URL Dispatcher (GSoC 2015 proposal)

Hi Marten, I think it would be helpful to motivate this with some pseudocode of specific use cases you are aiming to solve. Have you looked into whether there are any related third-party projects related to your ideas from which you could draw inspiration? Tim On Monday, March 2, 2015 at 11:5

Re: Suggestion: add default "registration/login.html" to django.contrib.auth

The admin templates extend "admin/base_site.html" and rely on the presence of specific template blocks so I don't think it's appropriate for those dependencies to be added to contrib.auth. I'm curious to see what content you would propose for a default template. Typically I've seen login templa

Re: does django-admin need a man page?

Is anyone interested in updating Django's man page? It's a bit embarrassing that the one that ships with 1.7 includes commands that no longer exist (cleanup, install (never heard of that one before), etc.). The fact that it is so outdated and that we've gotten no complaints about it is why I th

Re: GSOC 2015 project ideas suggestion

I have seen that error on my own system Ubuntu 14.04 & Python 3.4.2 (installed from source), but didn't investigate the cause. I just installed Python 3.4.3, however, and don't have the problem there. Now I've reinstalled 3.4.2 and the error is resolved there as well. On Thursday, March 5, 2015

Re: status of 1.8 release blockers

5, 2015 at 3:43:15 AM UTC-5, raulcd wrote: > > \o/ > > On Wed, Feb 25, 2015 at 1:08 AM, Tim Graham > wrote: > >> Zero blockers as of this writing. If we survive the next 12 hours with no >> new ones, I'll release the beta around then (famous last words). >>

Fellow Report - March 6, 2015

As you know if you saw Russ's recent post on the Django blog , the fellowship program has resumed as of this week. A big thank you to everyone who helped with the fundraising efforts and contributed to the

Re: Prospective GSOC applicant for 2015

Hi Acho, You'll need to research the various questions posed in the project description and come up with a proposal. It'll be easier to give you further guidance after that. You might want to take a look at the existing Trac tickets under the "Testing framework" component for related issues to

[ANNOUNCE] Security releases and advisory issued (1.7.6 and 1.8b2)

Today the Django team issued multiple releases -- Django 1.7.6 and 1.8b2 -- as part of our security process. These releases address a publicly reported security issue, and we encourage all users to upgrade as soon as possible. More details can be found on our blog: https://www.djangoproject.com

Re: GSOC 2015 project ideas suggestion

r > revamping django admin as a part of best practice update hoow about > extending django admin with the ideas from 3rd party apps llike djang admin > 2? or others. just for querying > > Regards > > On Fri, Mar 6, 2015 at 2:26 AM, Tim Graham > wrote: > >&g

1.9 release planning

With the release of 1.8 coming up, it's time to think about 1.9! I've suggested some dates below. The schedule is similar to the intervals we used for 1.8 with the final release date planned for about 6 months after 1.8 final (barring unforeseen delays, 1.8 will be released about 7 months after

Re: status of 1.8 release blockers

March 7, 2015 at 10:54:30 AM UTC-5, Tim Graham wrote: > > With about 10 days to go until the scheduled date for the release > candidate (Monday, March 16), there's just one blocker that Anssi's working > on (looks like tests aren't passing yet) [#24171]. About 7 issues

Re: Project Security Enhancements for Gsoc 2015

Hi Adhyan, If you don't have a background in security, I'd recommend a different project. I'm not too sure if we have a mentor for it either. Tim On Saturday, March 14, 2015 at 6:27:54 AM UTC-4, Adhyan Srivastava wrote: > > Hi, > I am Adhyan learning django from the past 6 months.During this ti

Re: Interested in GSoC idea "Replace Form Media Class"

files in contib.staticfiles might also be a concern in > this case. > > I am still discovering and learning new things about django and > preprocessing. I'd really appreciate if I'll be able to get feedback on > this from django community, so that I can draft a better pr

Re: Isomorphic Django?

I have not seen any discussion about such a thing. On Saturday, March 14, 2015 at 7:13:54 PM UTC-4, Benjamin Melki wrote: > > Hi are there any plans for isomorphic django version? > That runs python on both server and client (via transpiled js on the > client) like volt framework that appeared o

Fellow Report - March 13, 2015

We had the security release to start the week. There hasn't been much work to do for 1.8 release blockers, so mainly I've been going through the backlog of patches needing review and reviewing/merging them for 1.9. Report for week ending March 13, 2015: Triaged --- https://code.djangop

Re: Django Admin New Look

In some previous discussion, it was suggested to have a toggle between the new and old designs to ease the transition. I guess this could be something like a "theme" attribute on AdminSite. Do you think this is required? It seems this could be a non-trivial maintenance burden if we have to test

Re: GSOC 2015: Improving the less popular database backends

I like the idea of establishing a convention for discovering backend specific tests. As it is now, it seems that third-party backends need to have a customized version of Django's own runtests.py which duplicates a lot of code. Example for django-mssql: https://bitbucket.org/Manfre/django-mssql/

Re: GSoC 2015: Django Best Practices Update

gt; > Hi, > > Having a new thread for my gsoc project idea 2015. Analyzing for more then > a month I have decided to work on django best practices updates project. > Tim graham and Russels suggestions helped me to have some ideas related to > this project. In this thread

Re: Composite fields

Thomas, Please be patient. As for me, I'm focused on finishing up the 1.8 release. I've added composite fields and a link to your DEP to the 1.9 roadmap to help ensure it gets attention for that release cycle: https://code.djangoproject.com/wiki/Version1.9Roadmap On Wednesday, March 18, 2015 at

[ANNOUNCE] Security releases issued (1.4.20, 1.6.11, 1.7.7 and 1.8c1)

Today the Django team issued multiple releases -- Django 1.4.20, 1.6.11, 1.7.7, and 1.8c1 -- as part of our security process. These releases address a couple security issues, and we encourage all users to upgrade as soon as possible. More details can be found on our blog: https://www.djangopro

Re: Gsoc 2015

Unless you can pose some more specific questions, I think it's probably not a good choice for you. On Friday, March 20, 2015 at 4:20:15 AM UTC-4, Sharad Boni wrote: > > Hello, > > My name is Sharad Boni, currently in the third year of engineering > (Information Technology). > I want to contrib

improving debug logging in development

I think the lack of an obvious way to get a useful logging config for local development is a pain point we could address. Here's a patch from a contributor based on a blog post by Dan Poirier [1]: https://github.com/django/django/pull/4362 Do you think this is a good suggestion or do you have a

Fellow Report - March 20, 2015

Another round of security releases this week and lots of patch review for fixes and small features for 1.9 (and a couple small issues in 1.8). Report for week ending March 20, 2015: Triaged --- https://code.djangoproject.com/ticket/24490 - Add LogEntry.change_message when an object is

Re: GSOC 2015 project ideas suggestion

I see there's already a patch attached to the ticket that implements your proposal. While it likely needs to be updated to apply cleanly, I don't imagine that will take more than a few days? On Sunday, March 22, 2015 at 2:19:37 PM UTC-4, Asif Saifuddin wrote: > > Hi All, > > during my analyzing

Re: [GSoC] Security Dashboard

Hi Kevin, I'm not sure about the background of that idea, but it might be somewhat obsolete. In Django 1.8, we integrated django-secure and its security checks. These run as part of the system check framework: https://docs.djangoproject.com/en/1.8/ref/checks/#security I don't think really see

Re: GSOC 2015 project ideas suggestion

ntation and also getting ideas about the problems > people faced earlier and theie thoughts about the possible solutions :) > > I'm I in right direction? at least in some context? knowing that will help > me a lot > > ./auvipy > > > > On Mon, Mar 23, 2015 at 1:1

Re: improving debug logging in development

The alternative to a new setting would be to revert the "merging" behavior of the django.utils.log.DEFAULT_LOGGING and settings.LOGGING entirely. This original design was proposed by Claude in https://code.djangoproject.com/ticket/18993#comment:7, but now we realize disable_existing_loggers=Tru

Re: improving debug logging in development

Hm, now I wonder if that blog post in my initial post is entirely correct. This config seems to send all Django logging to stdout (regardless of the value of disable_existing_loggers). The difference from the initially proposed doc patch is that this config redefines the 'django' logger instead

Re: Help needed with Oracle GIS backend

I also advertised this on the geodjango mailing list with the following message : Do we have any users of the Oracle GIS backend that have interest and ability to help maintain it? Claude has worked on several issues for 1.9 t

Re: GSOC 2015 project ideas suggestion

ttps://gist.github.com/auvipy/1da0d96f826bd8da4d47 > <https://www.google.com/url?q=https%3A%2F%2Fgist.github.com%2Fauvipy%2F1da0d96f826bd8da4d47&sa=D&sntz=1&usg=AFQjCNHlxq1ON13Tox-sy1AS8_fkrDKzQg> > > On Mon, Mar 23, 2015 at 4:43 AM, Tim Graham > wrote: > >>

Re: Help needed with Oracle GIS backend

lity and in general to make it faster. > > It's currently closed source but we're working on to open source it > in hope that it could interest more wider audience (mainly because it > would enable GIS use with free Oracle XE). > > On Tue, 24 Mar 2015 04:48:38 -0700

Re: GSOC 2015 project ideas suggestion

It still doesn't interest me enough to provide any additional feedback. On Thursday, March 26, 2015 at 1:20:42 AM UTC-4, Asif Saifuddin wrote: > > Hi, > > I have been updating my proposal and as the deadline is friday Your > feedback will help me to make it better in technical point of view > > h

Re: Pre-DEP: community support of unmaintained versions of Django

Instructions for requesting to be added to the security prenotification list are here: https://docs.djangoproject.com/en/dev/internals/security/#requesting-notifications On Thursday, March 26, 2015 at 7:11:12 PM UTC-4, Christian Hammond wrote: > > Hi Carl, James, > > Sorry for the late reply on

Re: Pre-DEP: community support of unmaintained versions of Django

Sounds good to me. On Friday, March 27, 2015 at 12:28:09 PM UTC-4, Carl Meyer wrote: > > Hi Christian, > > On 03/26/2015 05:11 PM, Christian Hammond wrote: > > I know you guys are still sorting out how you want to run this, but I > > wanted to let you know that, given our current dependence on

Fellow Report - March 27, 2015

Not much out of the ordinary this week. We've fixed four small issues in the 1.8 branch since the release candidate (with no other reported blockers), so I am optimistic we’ll be able to release on Wednesday as scheduled. I’m also pleased that the unreviewed ticket queue (< 5 tickets) and pat

Re: status of 1.8 release blockers

We've fixed four small issues in the 1.8 branch since the release candidate (with no other reported blockers), so I am optimistic we’ll be able to release 1.8 final on Wednesday as scheduled. On Saturday, March 14, 2015 at 4:45:21 PM UTC-4, Tim Graham wrote: > > Good news: just one

[ANNOUNCE] Django 1.8 released

Django 1.8, the next long-term support release, is now available: https://www.djangoproject.com/weblog/2015/apr/01/release-18-final/ With the release of Django 1.8, Django 1.6 has reached end-of-life. As such, Django 1.6.11 is the final release of the 1.6 series. Django 1.7 will continue to rec

Re: 1.9 release planning

`if DJANGO_X_Y` conditionals. One idea is that third-party packages could declare their own "LTS" versions (if needed) and drop support for older versions more freely in future development. On Wednesday, March 11, 2015 at 8:13:11 PM UTC-4, Tim Graham wrote: > > With the release

Fellow Report - April 3, 2015

During the first half of the week I assisted with a couple of final bugs in 1.8. I also did some other release preparation tasks, like updating the djangoproject.com downloads page (which is mostly programatically generated) to accommodate two supported LTS versions (otherwise 1.4 would have

Re: 1.9 release planning

With a 9 month schedule, here is what the future might look like: 1.8 - April 2015 1.9 - January 2016 2.0 - October 2016 2.1 - July 2017 (LTS, and might be the last version to support Python 2.7 since 3 years of LTS support would cover until the 2020 sunset.) 2.2 - April 2018 Do you think there

Re: Wsgi Traceback on Django 1.8

This query came up on IRC a few days ago. I believe it was solved by clearing the site's cache. This is one of the recommended steps in "How to Upgrade Django." https://docs.djangoproject.com/en/dev/howto/upgrade-version/ On Thursday, April 9, 2015 at 1:14:35 AM UTC-4, Curtis Maloney wrote: > >

Fellow Report - April 11, 2015

On Monday, we finished migrating djangoproject.com to Python 3.4 (except Trac ). Thanks to Rolf Erik Lekang for most of the work there. Later in the week, I upgraded the Jenkins cluster to PostgreSQL 9.4 to support Marc Tamlyn's work of adding JSONField

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

I just discontinued the 1.3 docs on docs.djangoproject.com, they are still available on django.readthedocs.org. Do you think we should keep it there or not? On Thursday, August 7, 2014 at 7:45:15 AM UTC-4, Tim Graham wrote: > > I'm in favor of discontinuing older version of the docs.

Re: Why deprecate the ability to reverse using the Python path?

Please see the ticket and release notes: https://code.djangoproject.com/ticket/22384 https://docs.djangoproject.com/en/1.8/releases/1.8/#passing-a-dotted-path-to-reverse-and-url If you want to continue using dotted paths, you might be able to create a custom url() function that assigns a name usi

Re: Unneeded index created with unique=True and db_index=False in TextField

#19441 is the ticket where it was decided that unique=True implies a database index. The documentation says, "Note that when ``unique`` is ``True``, you don't need to specify`Field.db_index`, because ``unique`` implies the creation of an index." Unless we decide that is wrong, I think the cor

Re: Proposal: testdb cached by hash on migrations dirs

You might like to know about the --keepdb option in Django 1.8: https://docs.djangoproject.com/en/1.8/ref/django-admin/#django-admin-option---keepdb On Friday, April 17, 2015 at 6:04:00 PM UTC-4, Andrew Farrell wrote: > > Hi Folks, > > I've been working on speeding up a django-1.7 applications un

Idea/request for help: Django Developers Community Survey

I had an idea to conduct a survey to get a sense of how developers are using Django. I first had the idea when the question of maintenance of the Oracle GIS backend came up. We really have no idea whether or not anyone is actually using that backend, and it would be helpful to know so we are not

Request for help: building a docker/vagrant platform for running Django's test suite

In 2012, Julien Phalip started the djangocore-box project [1]: "A virtual machine for running the Django core test suite with every supported version of Python, every supported database backend and other dependencies." Unfortunately, the project hasn't seen an update in a year and a half, and I

Fellow Report - April 17, 2015

Report for week ending April 17, 2015: Triaged --- https://code.djangoproject.com/ticket/24634 - Comma as a cookie separator in HTTP_COOKIES is not handled correctly (invalid) https://code.djangoproject.com/ticket/24616 - date_hierarchy with USE_TZ=True won't work with Amazon RDS (accep

Re: Request for help: building a docker/vagrant platform for running Django's test suite

Hi John, Kevin and I are going to chat about it tonight. I'll keep this thread updated with ours plans and progress. Tim On Tuesday, April 21, 2015 at 1:00:46 PM UTC-4, John Giannelos wrote: > > Hey all, > > I would also be interested to contribute to this effort. > Is there a ticket/github iss

Re: Altering migration operations depending django.Version (3rd party apps)

The recommended way is to run makemigrations with the lowest version of Django you wish to support. As this recommendation hasn't been tested, let us know if you encounter any problems with it. A potential problem that comes to mind is if you have an EmailField which had its default max_length

Re: Altering migration operations depending django.Version (3rd party apps)

> ask the user to run "makemigrations" which doesn't seem right? > > On Wednesday, 22 April 2015 13:13:40 UTC+1, Tim Graham wrote: >> >> The recommended way is to run makemigrations with the lowest version of >> Django you wish to support. As this reco

Re: Pass exception to error handlers

I have some concerns from a security standpoint. For example, some exception messages are definitely not meant to be displayed to end users and may leak server implementation details. For example: SuspiciousFileOperation( 'The joined path ({}) is located outside of the base path ' 'compo

Re: Writing some tests for new feature

I'll copy my reply from your django-users thread in case you didn't see it: There was some recent work done on allowing customizing the ping_google sitemap URL, but it wasn't completed: https://github.com/django/django/pull/3528 You could take inspiration from your tests from there. On Wednesd

Re: Idea/request for help: Django Developers Community Survey

co > > > On Saturday, April 18, 2015 at 1:00:13 AM UTC+2, Tim Graham wrote: >> >> I had an idea to conduct a survey to get a sense of how developers are >> using Django. I first had the idea when the question of maintenance of the >> Oracle GIS backend came up

Re: System check is using the default database connection for all the models

It seems like a bug to me. If I had to guess, I'd say it's a multi-database setup that no one thought to test when the system check framework was developed. On Friday, April 24, 2015 at 3:49:03 PM UTC-4, Ion Scerbatiuc wrote: > > Hello, > > Wasn't sure if this is a bug or not, and I couldn't fin

Fellow Report - April 24, 2015

I am thinking that if all goes well, we will probably release a 1.8.1 bug fix release by next Friday. Currently we have about 20 fixes for that release. Report for week ending April 24, 2015: Triaged --- https://code.djangoproject.com/ticket/24668 - Update docs example code for ModelAdmi

Re: Idea/request for help: Django Developers Community Survey

> Am 25.04.2015 14:29, schrieb Tim Graham: > > Aymeric and I put together a draft: > > > https://docs.google.com/forms/d/1Owv-Y_beohyCm9o2xPamdBnvjreNYoWai3rDloKZxWw/viewform > > All questions are optional so you can just click through it to view the > questions. We&#

Re: System check is using the default database connection for all the models

: > > I'll try to get a PR/proposal to fix the issue as soon as I get some free > time this week. > > Should I also submit a bug here? https://code.djangoproject.com > > Thanks, > Ion > > On Saturday, April 25, 2015 at 5:00:02 PM UTC-7, Tim Graham wrote: >> >&g

Re: Translation documentation wrong import

Thanks. For future reference, we don't need a message to this list in order to know when a pull request is opened. On Tuesday, April 28, 2015 at 1:16:28 PM UTC-4, Mounir Messelmeni wrote: > > I've opened a pull request for fixing an import on the translation > documentation, I just changed ugett

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