In ticket #27683 [0], Shai proposed to change Django to default to using
the READ COMMITTED isolation level. Some background on the reasons are on
the ticket and in another thread [1] (possible data loss is involved).
The initial approach [2] that Shai put forward is adding a deprecation
warnin
rate the
>> point that it is not a reasonable assumption that all 3.5 installs use
>> OpenSSL libraries.
>>
>> On Monday, January 9, 2017 at 7:39:18 PM UTC-5, Tim Graham wrote:
>>>
>>> About "we cannot just assume that all Python 3 installs have a "fa
We cannot use the name "QuerySet.except()" since except is a reserved word
in Python. Do you prefer minus() (as suggested by Florian), except_() (as
done by SQLAlchemy), or something else?
On Monday, December 26, 2016 at 6:28:15 PM UTC-5, Adam Johnson wrote:
>
> Yes it's different, they cannot b
A question about the casing. Since "subquery" is one word, I wouldn't camel
case it like SubQuery. Any other opinions?
Josh says, "I prefer the CamelCased SubQuery visually. Subquery looks
strange to me, even if it technically can be one word."
On Wednesday, April 20, 2016 at 3:06:06 AM UTC-4,
Please avoid the temptation to use this mailing list as a second level
support channel. Imagine if everyone did that.
On Thursday, January 12, 2017 at 7:09:48 AM UTC-5, Ali khan wrote:
>
> Hi All,
> I know this is not the platform and I apologize to bother you all. But
> I've posted on stackover
e.
>
> Here is my view on why using a compatibility layer in Django (or any
> framework, actually) would be a good idea :
>
> PROs:
> - cleaner django codebase
> - less work to deprecate features
> - automated checks of compatibility between django version
> - easily achie
I guess three days is too little time to get a consensus on this. At this
point I'm thinking to defer this from 1.11.
On Wednesday, January 11, 2017 at 9:50:27 AM UTC-5, Patryk Zawadzki wrote:
>
> To add some context, REPEATABLE READ can break get_or_create among other
> things (not sure how man
ssue, I think it’s fair to let him make the final call
>> and keep the deprecation path if he thinks that’s safer.
>>
>> Regardless, I’d love if this fix made it into 1.10, let’s not delay it
>> because we’re worried of being too cautious :-)
>>
>> --
>>
Triaged
---
https://code.djangoproject.com/ticket/27689 -
FileSystemStorage().get_valid_name() may return empty string (wonfix)
https://code.djangoproject.com/ticket/27703 - Template language type
annotations (needsinfo)
https://code.djangoproject.com/ticket/27701 - Document that runser
There is also a ticket: https://code.djangoproject.com/ticket/25612
"django.contrib.auth should include support for 2fa out of the box".
On Sunday, January 15, 2017 at 6:22:30 AM UTC-5, Florian Apolloner wrote:
>
> Hi,
>
> yes we'd very much like to have 2fa in Django. At the minimum we'd like to
fate" button on
>> djangoproject.com would attract much more attention to the issue. Maybe
>> most of Django users are ready to migrate to Python 3.6 when they switch to
>> Django 2.0 (probably not, but who knows) and developers could start
>> enjoying new Python featu
I've reviewed and merged as much as I can (thank you to everyone who
helped!) and plan to create the stable/1.11.x branch and issue the alpha
release in approximately 7 hours.
On Monday, December 26, 2016 at 1:17:01 PM UTC-5, Tom Christie wrote:
>
> >
> this feature https://github.com/django/dj
We've made the first release on the way to Django's next major release,
Django 1.11! With two and a half months until the scheduled final release,
we'll need timely testing from the community to ensure an on-time and
stable release. Check out the blog post:
https://www.djangoproject.com/weblog/
I increased the iterations to 100,000 on master (targeting Django 2.0). It
would be nice to determine a guideline for how to determine future
increases.
On Monday, January 16, 2017 at 12:55:25 PM UTC-5, Martin Koistinen wrote:
>
> Tobias,
>
> Thanks for the comprehensive benchmarking and summary
I've submitted our organization application for this year.
Anyone interested in mentoring, please indicate your interest
https://code.djangoproject.com/wiki/SummerOfCode2017. Any experienced
contributors are welcome to mentor. We also need project ideas on that
page. I've copied the ideas from
As we worked on removing Python 2 compatibility code from master this week
[0], we collected a number of import shims and functions that are only
needed for code that wants to support Python 2 [1].
So far there is django.utils.six, as well as some undocumented things:
- django.utils.lru_cach
2017 at 4:41:59 PM UTC-5, Shai Berger wrote:
>
> On Saturday 21 January 2017 22:55:51 Tim Graham wrote:
> >
> > I'm advocating to remove the undocumented things in Django 3.0 (released
> > Dec. 2019) or later without a deprecation. By that time, I hope
> third-pa
Triaged
---
https://code.djangoproject.com/ticket/27730 - Document that template tags
with "as" variable assignment don't propogate variables across blocks
(accepted)
https://code.djangoproject.com/ticket/27742 - Unexpected migration on
Parent -> child model inheritence (accepted)
http
The 'django.db.backends.postgresql' alias was added in Django 1.9 along
with import shims in the old location:
django.db.backends.postgresql_psycopg2 [0]. I'd like to remove the import
shims at some point [1] (but keep the two line shim in django/db/utils.py
that allows using DATABASES 'ENGINE'
I'm not sure offhand. Could you provide a link to the issue so we could
look at the details?
On Monday, January 23, 2017 at 1:45:48 PM UTC-5, Andrew Godwin wrote:
>
> An interesting bug has turned up in Channels where someone is trying to
> remove a session using .flush(), but our decorator sees
something that
> wraps a consumer, loading a session on the way in and saving it on the way
> out if it changed, similar to how session middleware might work.
>
> Andrew
>
> On Mon, Jan 23, 2017 at 11:57 AM, Tim Graham > wrote:
>
>> I'm not sure offhand. Could you pro
Okay, I updated the PR to use a deprecation. I'd rather not complicate
things with an accelerated deprecation.
On Tuesday, January 24, 2017 at 6:39:32 AM UTC-5, Adam Johnson wrote:
>
> Ok fair point, I agree it should go through the short deprecation process.
> It's also very small and not that
Try adding this to both entries in your DATABASES test settings:
'TEST': {
'CHARSET': 'utf8',
'COLLATION': 'utf8_general_ci',
},
On Wednesday, January 25, 2017 at 7:36:41 AM UTC-5, JA Robson wrote:
>
> hi, I'm on OSX (Sierra), am running a local MySQL, version 5.7.17, running
> django '2
to know how can one help in testing for the final release?
>
> Using the new features in small projects or is there a formal procedure
> for testing?
>
> On Wednesday, January 18, 2017 at 6:48:18 AM UTC+5:30, Tim Graham wrote:
>>
>> We've made the first release on the
python_2_unicode_compatible, which was a
>> public API until it got merged into six and we started using six’ version.
>>
>> I’m +0 on deprecating rather than removing modules that a developer of a
>> pluggable app would reasonably use for Python 2 compatibility, such
>> as django
A difference is that a deprecation starting in 2.2 is in 2 releases (2.2,
2.3) while the deprecation starting in 3.0 is in 3 releases (3.0, 3.1, 3.2).
On Wednesday, January 25, 2017 at 10:30:40 AM UTC-5, Aymeric Augustin wrote:
>
> Hello Tim,
>
> On 25 Jan 2017, at 16:11, Tim Graha
t to the ideas page?
>
> On Saturday, 21 January 2017 02:27:33 UTC+5:30, Tim Graham wrote:
>>
>> I've submitted our organization application for this year.
>>
>> Anyone interested in mentoring, please indicate your interest
>> https://code.djangoproject.com/
Did you check if the manager changes in Django 1.10 could help? (By the
way, usage questions should be asked on the django-users list).
https://docs.djangoproject.com/en/stable/releases/1.10/#manager-use-for-related-fields-and-inheritance-changes
On Wednesday, January 25, 2017 at 10:36:58 AM UTC-
There were more cleanups for the removal of Python 2 this week:
https://code.djangoproject.com/ticket/23919. I think it’s mostly done now.
Triaged
---
https://code.djangoproject.com/ticket/27765 - Migration to delete child
model (multi-table inheritance) results in an error when using SQ
Hi, could you point to where the problematic storage.listdir() call is in
Django?
On Monday, January 30, 2017 at 11:02:32 AM UTC-5, Melvyn Sopacua wrote:
>
> Hello,
>
>
>
> the current Storage API has some inconsistencies and in short it's
> impossible to write anything that requires a directo
I meant: where does Django call that method that's causing a problem for
your use case?
On Monday, January 30, 2017 at 11:43:27 AM UTC-5, Melvyn Sopacua wrote:
>
> On Monday 30 January 2017 08:16:20 Tim Graham wrote:
>
> > Hi, could you point to where the problematic stora
Hi Gert, I think the renderer API could be used for this use case. Did you
look at that?
https://docs.djangoproject.com/en/dev/ref/forms/renderers/#the-low-level-render-api
On Wednesday, February 1, 2017 at 6:05:08 AM UTC-5, Gert Steyn wrote:
>
> Hi All
>
> I got very excited when I read about t
this mailing list the right place?
>
> On Saturday, January 21, 2017 at 2:27:33 AM UTC+5:30, Tim Graham wrote:
>>
>> I've submitted our organization application for this year.
>>
>> Anyone interested in mentoring, please indicate your interest
>>
There's an old accepted ticket for it:
https://code.djangoproject.com/ticket/16922. Reviewing the past discussion
may help you refine your proposal.
On Friday, February 3, 2017 at 6:01:11 AM UTC-5, Gert Steyn wrote:
>
> Hi All
>
> Is anybody against using the new renderers (used to render widget
#21461 proposes to add signals for QuerySet.update(). Would this solve your
use case?
https://code.djangoproject.com/ticket/21461
On Friday, February 3, 2017 at 12:14:23 PM UTC-5, mtnpaul wrote:
>
> Good to know.
>
> Thanks,
>
> Paul
>
>
> On Fri, Feb 3, 2017 at 10:03 AM, Oskar Persson > wrote
Triaged
---
https://code.djangoproject.com/ticket/27797 - dumpdata generate a backup
not usable with loaddata using MySQL (wontfix)
https://code.djangoproject.com/ticket/27792 - Extended category support for
Atom and RSS feeds (accepted)
https://code.djangoproject.com/ticket/2 - Fil
e a bigger issue since
> then you probably *need* the updated objects, which I'm not including
>
> Den fredag 3 februari 2017 kl. 18:21:55 UTC+1 skrev Tim Graham:
>>
>> #21461 proposes to add signals for QuerySet.update(). Would this solve
>> your use case?
>>
&
>> all the problems that the update signals does but they solve some of them
>> without having any real impact on performance.
>>
>> Den måndag 6 februari 2017 kl. 03:00:18 UTC+1 skrev Tim Graham:
>>>
>>> Since you created a ticket [0], I assume you feel there
with the
> instance of B. Then if we come up with a solution for QuerySet.update() we
> could also send a signal with all objects from A. So I'm not sure I think
> its redundant in that way.
>
> Den måndag 6 februari 2017 kl. 14:23:31 UTC+1 skrev Tim Graham:
>>
>&
> would have to look through the fields that it's updating and check if its a
> foreign key and then send the signals for those elements some how
>
> Den måndag 6 februari 2017 kl. 18:18:39 UTC+1 skrev Tim Graham:
>>
>> Tell me if I'm wrong because I haven't w
That looks like an oversight in the class-based view conversion [0].
Probably LoginView() needs a get_form_kwargs() method. Would you like to
create a ticket and provide a patch?
[0]
https://github.com/django/django/commit/78963495d0caadb77eb97ccf319ef0ba3b204fb5
On Monday, February 6, 2017 at
Since that's a release blocker for a feature that hasn't been released yet,
it's fine to reference/reopen the original ticket rather than create a new
one. I've created a PR, https://github.com/django/django/pull/8034.
On Wednesday, February 8, 2017 at 7:40:02 AM UTC-5, Adam Johnson wrote:
>
> P
I thought the mixin idea was good but everyone else (including Aymeric)
reviewed the pull request and ignored your comment about that so I assumed
no one else saw its merits. Considering a CITextField that uses CharField
still has some usefulness as you mentioned, I'm in favor of CITextField not
- would this be a better approach?
>
> On Wednesday, February 8, 2017 at 6:09:26 PM UTC+1, Tim Graham wrote:
>>
>> I thought the mixin idea was good but everyone else (including Aymeric)
>> reviewed the pull request and ignored your comment about that so I assumed
>> no o
1.11.
On Tuesday, January 17, 2017 at 11:20:36 AM UTC-5, Tim Graham wrote:
>
> I've reviewed and merged as much as I can (thank you to everyone who
> helped!) and plan to create the stable/1.11.x branch and issue the alpha
> release in approximately 7 hours.
>
> On Monda
Triaged
---
https://code.djangoproject.com/ticket/27810 - Add query expression support
for ModelAdmin list_display's admin_order_field (accepted)
https://code.djangoproject.com/ticket/27812 - When there is a DateTimeField
django does not group by (invalid)
https://code.djangoproject.com
Once in a while, there's a ticket about this behavior:
m = Model(decimal='12.9')
m.save()
self.assertEqual(m.decimal, '12.9')
m.refresh_from_db()
self.assertEqual(m.decimal, Decimal('12.9'))
That is, you can create a model with an incorrect type and it won't be
fixed until you refresh the object
Adam, here's a ticket about allowing custom Meta attributes:
https://code.djangoproject.com/ticket/5793. I guess it would be better to
have a separate thread for that discussion.
On Tuesday, February 14, 2017 at 6:22:08 PM UTC-5, Adam Johnson wrote:
>
> Sorry for the terrible pun here, but I'd l
Hi Raphael,
It looks like a similar idea was proposed in
https://groups.google.com/d/topic/django-developers/C1L-NhyQYG4/discussion.
I don't think a ticket was ever created, so you can do that.
100% test coverage is required. Why would we accept untested code? ;-)
On Wednesday, February 15, 20
Yes, if a ticket goes weeks or months without activity, it's unlikely
someone is working on it, so it's fine to reassign.
On Wednesday, February 15, 2017 at 9:11:01 PM UTC-5, Robert Roskam wrote:
>
> Hey All,
>
> So it's over a year later, and even though there is consensus, this ticket
> (https
These questions involving old code aren't always easily answered. I would
try to answer it by looking through git blame and finding the relative
commits and tickets to see if there's an explanation there.
On Wednesday, February 15, 2017 at 8:07:45 PM UTC-5, Danielle Madeley wrote:
>
> Hi all,
>
After reviewing the pull request, I wonder if it would be better to raise
exceptions when comparing nonexistent variables in {% if %} rather than
altering the behavior. For existing projects, this would prevent possible
inadvertent information leakage if some {% if %} starts evaluating
differen
Hi Etienne, I'm not sure exactly what type of response you're looking for
or if this is on-topic for the Django developers mailing list, which
pertains to the development of Django itself. django-users seems more
appropriate unless you're proposing some feature for Django.
On Friday, February 1
> expected to be dropped before the next Django LTS will be released, so
> please keep that in your project planning." (Language too informal, but I
> think the idea is correct.)
>
>
>
> On Wed, Jan 18, 2017 at 2:28 AM, Claude Paroz > wrote:
>
>> Le mardi 17 janv
Hi, please see this thread for guidance:
https://groups.google.com/d/topic/django-developers/8qvrKfZaP2o/discussion
On Saturday, February 18, 2017 at 9:26:37 AM UTC-5, Vipin Chaudhary wrote:
>
> Hi all,
>
>
> little intro,
>
>
> I am Vipin Chaudhary , a CSE undergrad in IIIT Delhi, India. I am a
; good knowledge about it
>
> Thanks
>
> On Saturday, January 21, 2017 at 2:27:33 AM UTC+5:30, Tim Graham wrote:
>>
>> I've submitted our organization application for this year.
>>
>> Anyone interested in mentoring, please indicate your interest
>> ht
Triaged
---
https://code.djangoproject.com/ticket/27830 - Use
distutils.version.LooseVersion instead of custom version parsing (accepted)
https://code.djangoproject.com/ticket/27832 - contenttypes migration not
following the doc on hints naming (accepted)
https://code.djangoproject.com/
In partnership with the freenode community team, the Django team will hold
an "Ask Me Anything" session this week.
See http://freenode.net/news/django-ama for details.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itse
We've made the second release on the way to Django's next major release,
Django 1.11! With a month and a half until the final release, we'll need
timely testing from the community to ensure an on-time and stable release.
Check out the blog post:
https://www.djangoproject.com/weblog/2017/feb/20/
This is starting in about 30 minutes. Any Django team members who want to
participate in the question answering, please ping me on IRC.
On Monday, February 20, 2017 at 9:02:38 AM UTC-5, Tim Graham wrote:
>
> In partnership with the freenode community team, the Django team will hold
> a
Hi, There is no need to write to this mailing list when you open a ticket,
and there is no need to address your correspondence to me personally.
Thanks!
On Thursday, February 23, 2017 at 7:15:09 AM UTC-5, Vipin Chaudhary wrote:
>
> Hi,
>
> I opened a new ticket https://code.djangoproject.com/tic
I think any use of undefined template variables should raise an exception.
In the long run, keeping a setting to allow some other behavior seems
confusing and, considering the case of templates that might be reused in
different projects with different settings, even dangerous.
On Saturday, Febr
:44:30 PM UTC-5, Karen Tracey wrote:
>
> On Sat, Feb 25, 2017 at 2:10 PM, Tim Graham > wrote:
>
>> I think any use of undefined template variables should raise an
>> exception. In the long run, keeping a setting to allow some other behavior
>> seems confusing and, co
Triaged
---
https://code.djangoproject.com/ticket/27860 - Changing a CharField to a
ForeignKey crashes when migrating in PostgreSQL (accepted)
https://code.djangoproject.com/ticket/27858 - Stop read-only management
commands from attempting to create a django_migrations table (accepted)
test framework cleanup, do you think it
> would be more useful than NoSQL idea?
>
> Alexandra and Alexandra
>
> пн, 27 февр. 2017 г. в 15:30, Tim Graham :
>>
>> Hi Alexandra and Alexandra,
>>
>> I'm not sure what exactly the NoSQL idea would entail but I pe
:57:33 PM UTC-5, Tim Graham wrote:
>
> I've submitted our organization application for this year.
>
> Anyone interested in mentoring, please indicate your interest
> https://code.djangoproject.com/wiki/SummerOfCode2017. Any experienced
> contributors are welcome to mento
Details are available on the Django project weblog:
https://www.djangoproject.com/weblog/2017/mar/01/bugfix-release/
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop
Could you explain the use case a bit more? Why is your database failing on
a regular basis?
On Wednesday, March 1, 2017 at 4:00:12 PM UTC-5, James Pic wrote:
>
> Hi all,
>
> It seems like runserver won't retry to connect to the database after a
> failing connection. Once the db server is up, it
I don't know. Can you propose a patch so we can see what's involved? How
would a "production" web server (nginx, apache, etc.) handle the issue?
I'm more interested in moving runserver toward using gunicorn [0] (Windows
support seems the main blocker to proceeding there) than adding more
featur
Hi Maitreya,
If you haven't contributed to Django by now, that project is likely too
ambitious. You should choose a project where you can at least answer the
question "how do I get started?"
On Friday, March 3, 2017 at 7:26:45 AM UTC-5, Maitreya Verma wrote:
>
> Hello,
> I am Maitreya Verma, a
think would be a better use of time?" that's
something I could advise about.
On Tue, Feb 28, 2017 at 10:08 AM, Александра Мартынова
wrote:
> Yes, we would like to know about the most useful tickets, thank you.
>
> Alexandra and Alexandra
>
> 2017-02-27 23:15 GMT+03:00 Tim
There is probably a summer's worth of work to do outside of the work that's
already happening, so if you want to add something to the ideas page, that
sounds good to me.
On Saturday, March 4, 2017 at 12:52:01 AM UTC-5, akki wrote:
>
> @Josh Absolutely correct. I meant since this involves a lot o
Hi Michael, it looks like we're not enhancing send_mass_mail() as per the
docstring [0]: "The API for this method is frozen. New code wanting to
extend the functionality should use the EmailMessage class directly."
Perhaps the documentation could be clarified.
[0]
https://github.com/django/dja
Triaged
---
https://code.djangoproject.com/ticket/27882 - Allow template fragment
caching for unlimited time (accepted)
https://code.djangoproject.com/ticket/27884 - Document that validators
needs to be an iterable since Django 1.11 (wontfix)
https://code.djangoproject.com/ticket/27888
Have you read the wiki page?
https://code.djangoproject.com/wiki/SummerOfCode2017 It contains getting
started tips. If so, please be more specific with your questions.
On Sunday, March 5, 2017 at 11:11:17 AM UTC-5, Pranav Jadhav wrote:
>
> Hey Tim,
> I am Pranav Jadhav, an undergrad student
Hi, Have you read the wiki page?
https://code.djangoproject.com/wiki/SummerOfCode2017 It contains getting
started tips. If so, please be more specific with your questions.
On Monday, March 6, 2017 at 7:25:31 AM UTC-5, sahil jain wrote:
>
> Hello Everyone
> I am a sophomore major in computer scie
gt; between forms and models:
>
> On Saturday, April 2, 2016 at 10:44:44 AM UTC+2, Florian Apolloner wrote:
> > On Thursday, March 17, 2016 at 2:17:40 PM UTC+1, Tim Graham wrote:
> > > It seems useful, but I'm not sure if it increases the coupling between
> model an
The behavior of runserver hanging on a check error seems fine to me. That
gives you an opportunity to fix the error without having to manually
restart the server afterward -- just the same as if you had a SyntaxError.
Am I missing the reason why the behavior is problematic?
On Tuesday, March 7,
Hi, I'm surprised if the search behavior is nondeterministic rather than
searching STATICFILES_DIRS in order. If that's really the case, it seems
like a bug. Can you point to the code that causes the nondeterminism?
On Friday, March 10, 2017 at 7:35:25 AM UTC-5, Radosław Orłowski wrote:
>
> Righ
For the error, "Database returned an invalid datetime value. Are time zone
definitions for your database installed?", see
https://docs.djangoproject.com/en/dev/ref/databases/#time-zone-definitions.
Adding this to the 'default' and 'other' dictionaries in DATABASES may
solve some of the encoding
Triaged
---
https://code.djangoproject.com/ticket/27916 - versionchanged / versionadded
annotation titles missing in downloadable docs (accepted)
https://code.djangoproject.com/ticket/27910 - Allow using an Enum class in
model Field choices (wontfix)
https://code.djangoproject.com/ticke
Hi, I think the issue is described in
https://code.djangoproject.com/ticket/24182.
On Tuesday, March 14, 2017 at 12:50:52 PM UTC-4, Dylan Young wrote:
>
> Steps to reproduce:
>
> Create Model
> Make migrations
> Add FK to model with a callable default that has some side effect (e.g.
> creating t
Ticket #18773 [0] added logging of undefined template variables in Django
1.9 [1], however, I've seen several reports of users finding this logging
more confusing than helpful. For example, admin templates log errors about
missing is_popup variables [2] which is how the template are designed
(i
Welcome! It's a bit late to be starting on a successful proposal,
especially if you haven't contributed to Django before, but good luck. I'm
not sure if you were looking for anything specific in reply to your intro?
On Monday, March 13, 2017 at 9:52:34 AM UTC-4, Gunpreet Ahuja wrote:
>
> Greetin
Hi, I don't know anything about CTE, but did you see this third-party
package? https://github.com/petrounias/django-cte-trees -- It seems to be
PostgreSQL only.
I was going to write, "Considering that not all databases support CTE
(MySQL doesn't), a third-party app might be the way to go rather
5:14:34 PM UTC-5, Tim Graham wrote:
>
> Thank you to everyone who's tested their apps with Django 1.11. The beta
> release is planned for Monday, February 20. After that, only release
> blocking bug fixes will be accepted on the stable/1.11.x branch. There are
> currently no r
Triaged
---
https://code.djangoproject.com/ticket/27931 - Clarify the meaning of
"django catch-all logger" (accepted)
https://code.djangoproject.com/ticket/27937 - Potential issue with
field.queryset._result_cache persisting (reopened ticket that caused the
regression)
https://code.dja
It could be a suitable project, however, it's too late to develop a
proposal of that complexity for this summer. A prospective student would
need to demonstrate significant understanding of the ORM before I would
advise them to tackle that topic.
On Sunday, March 19, 2017 at 1:16:02 PM UTC-4, A
We're not quite down with blockers -- one was reported a few hours ago, so
I'm postponing the RC until tomorrow.
On Saturday, March 18, 2017 at 7:49:43 PM UTC-4, Tim Graham wrote:
>
> A handful of blockers (mostly in the final stages) remain as of right now
> [0]. We'
We've made the final (hopefully) release on the way to Django's next major
release, Django 1.11! Check out the blog post:
https://www.djangoproject.com/weblog/2017/mar/21/django-111-rc-1-released/
--
You received this message because you are subscribed to the Google Groups
"Django developers
This is already implemented in Django 1.11:
https://code.djangoproject.com/ticket/27061.
On Wednesday, March 22, 2017 at 6:53:11 AM UTC-4, Melvyn Sopacua wrote:
>
> Hi,
>
>
>
> I'm currently running into the problem that in order to run tests, I need
> to grant my database user super-user priv
Please search this mailing list's archives for past discussions, e.g.
https://groups.google.com/d/topic/django-developers/trTEbURFhEY/discussion.
On Wednesday, March 22, 2017 at 8:43:22 AM UTC-4, matthaus woolard wrote:
>
>
> Django 2 will be for python 3.5+ this is the perfect time to start
> a
I don't think the current fields are so bad or nonsensical that it warrants
a change. Also, consider that every Django user would have to learn how to
use a new permissions setup.
If you don't like the default permissions structure, use a custom user
model.
On Friday, March 24, 2017 at 7:31:32
Triaged
---
https://code.djangoproject.com/ticket/27958 - CSRF_COOKIE reset while
requesting a broken relative URL over HTTPS (invalid)
https://code.djangoproject.com/ticket/27970 - Allow in_bulk() to use other
unique fields besides the primary key (accepted)
https://code.djangoproject.
There's an accepted ticket about adding pre_update and post_update signals:
https://code.djangoproject.com/ticket/21461. From a quick glance, I think
this is what you're proposing.
On Thursday, March 30, 2017 at 4:28:00 PM UTC-4, Todor Velichkov wrote:
>
> Consider the following piece of code:
>
Triaged
---
https://code.djangoproject.com/ticket/27993 - Impossible to clear an
ArrayField with a forms.MultipleChoiceField (accepted)
https://code.djangoproject.com/ticket/27991 - Add 'obj' kwarg to
InlineModelAdmin's.has_add_permission() (accepted)
https://code.djangoproject.com/tick
Today the Django team issued 1.10.7, 1.9.13, and 1.8.18 as part of our
security process. These releases address two security issues, and we
encourage all users to upgrade as soon as possible:
https://www.djangoproject.com/weblog/2017/apr/04/security-releases/
As a reminder, we ask that potentia
Django 1.11, the next long-term support release, is now available:
https://www.djangoproject.com/weblog/2017/apr/04/django-111-released/
With the release of Django 1.11, Django 1.10 has reached the end of
mainstream support. The final minor bugfix release (1.10.7) was issued
today. Django 1.10
Hi, this was already wontfixed here:
https://code.djangoproject.com/ticket/3362
with the rationale, "We've decided in the past not to add a new class for
every single response code. You can already pass the status code in when
creating the HttpResponse class, so that can be used in this case."
I'd suggest to use git bisect to find the Django commit where the behavior
changed:
https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/#bisecting-a-regression
On Wednesday, April 5, 2017 at 5:57:03 PM UTC-4, Maximiliano Robaina wrote:
>
> Hi,
>
>
> I'm the maintener of
1501 - 1600 of 1659 matches
Mail list logo
