Django

Django: Under the Hood is back for its third edition! DUTH is an annual Django conference that takes place in Amsterdam, the Netherlands. On 3rd - 6th November this year, we're going to see 9 deep dive talks into topics of Django channels, testing ... [More] , Open Source funding, JavaScript, Django forms validation, debugging and many more. Django: Under the Hood also gives the opportunity to bring many Django core developers to work together and shape the future of Django with a group of 300 passionate Django developers attending the conference. This year, the registration process for the conference became a lottery to avoid mad rush and tickets selling out in minutes. Registration You can register now, and the lottery is only open until 26th of July at noon Amsterdam time. If you want to make sure that tickets for your team are reserved and set aside, Django: Under the Hood still has few sponsorship opportunities open. Please get in touch on [email protected]. [Less]

Almost exactly three years ago Django community adopted a Code of Conduct, we were one of the first communities to do so in the tech industry. Since then, we have come a long way and learned about how to effectively enforce the Code of Conduct. Today ... [More] we're proud to open source the documentation that describes how the Django Code of Conduct committee enforces our Code of Conduct. This documentation covers the structure of Code of Conduct committee membership, the process of handling Code of Conduct violations, our decision making process, record keeping, and transparency. In addition, we're also publishing summarized statistics about Code of Conduct issues handled by the committee thus far. We're hoping this is just the beginning of making our work more transparent to the wider community. We believe this documentation will help keep ourselves accountable to the Django community, as well as offer an insight into how decisions are made and issues are dealt with. We also hope that sharing our experiences is going to help other communities to not only adopt, but also implement and enforce the Code of Conduct. The DSF Code of Conduct committee looks forward to your feedback and contributions! [Less]

In accordance with our security release policy, the Django team is issuing Django 1.10 release candidate 1, Django 1.9.8 and 1.8.14. These release addresses a security issue detailed below. We encourage all users of Django to upgrade as soon as ... [More] possible. The Django master branch is also updated. Django 1.10 is now at release candidate stage. This marks the string freeze and the call for translators to submit translations. Provided no major bugs are discovered that can't be solved in the next two weeks, 1.10 final will be issued on or around August 1. Any delays will be communicated on the django-developers mailing list thread. CVE-2016-6186: XSS in admin's add/change related popup Unsafe usage of JavaScript's Element.innerHTML could result in XSS in the admin's add/change related popup. Element.textContent is now used to prevent execution of the data. The debug view also used innerHTML. Although a security issue wasn't identified there, out of an abundance of caution it's also updated to use textContent. Thanks Vulnerability Laboratory for reporting the issue and Paulo Alvarado for forwarding it to us. Affected supported versions Django master development branch Django 1.10 (now at release candidate status) Django 1.9 Django 1.8 Per our supported versions policy, Django 1.7 and older are no longer receiving security updates. Resolution Patches to resolve the issues have been applied to Django's master development branch and the 1.10, 1.9, and 1.8 release branches. The patches may be obtained from the following changesets: On the development master branch On the 1.10 release branch On the 1.9 release branch On the 1.8 release branch The following new releases have been issued: Django 1.10rc1 (download Django 1.10rc1 | 1.10rc1 checksums) Django 1.9.8 (download Django 1.9.8 | 1.9.8 checksums) Django 1.8.14 (download Django 1.8.14 | 1.8.14 checksums) The PGP key ID used for these releases is Tim Graham: 1E8ABDC773EDE252. General notes regarding security reporting As always, we ask that potential security issues be reported via private email to [email protected], and not via Django's Trac instance or the django-developers list. Please see our security policies for further information. [Less]

So far hundreds of supporting developers have purchased PyCharm at a 30% discount with the proceeds going to help support the Django Software Foundation. Considering the campaign is so successful, JetBrains and the DSF have opted to extend the offer ... [More] until July 20th! Which coincidentally will cover most of DjangoCon 2016. Everyone in the DSF would like to thank all of the many supports who have taken advantage of this great offer to help fund Django development and related activities into the future. Please spread the word to your friends and colleagues and perhaps we can make this fundraiser one of our largest yet! Get PyCharm now for 30% off and help support the Django Software Foundation! [Less]

Today and for the next two weeks, our fundraising program is getting a big boost from JetBrains PyCharm, a premiere Python IDE that has supported Django for many years. During this campaign, buy PyCharm Professional Edition with a 30% discount and ... [More] all money raised will go to our general fundraising and Django Fellowship program. Additionally, JetBrains is sponsoring PEP 484 type hinting in Django through a separate DSF Fellowship grant. “Django has grown to be a world-class web framework, and coupled with PyCharm’s Django support, we can give tremendous developer productivity,” says Frank Wiles. “The DSF helps make this growth happen, and we are delighted to have JetBrains support in our fundraising.” “For six years, Django has been the stable rock in our feature set. We share common ideals, and the success of Django is invaluable for us as well as for the whole Python community,” says Dmitry Filippov, JetBrains Product Marketing Manager. “This promotion gives us an opportunity to strengthen PyCharm’s relationship with Django by helping the DSF reach its fully-funded campaign goal.” Take Advantage of the Promotion During this two-week promotion, you can effectively contribute* to Django by purchasing an Individual PyCharm Professional annual subscription at a 30% discount: Click this link to go to the PyCharm annual subscription page. On the check-out page, сlick “Have a discount code?”. Enter this 30% discount promo code: IDONATETODJANGO Fill in other required fields on the page and click the “Place order” button. Read more details on the special promotion page. Again, all proceeds from this promotion will go to the DSF fundraising campaign—not just the profits, but actually the entire sales amount. The funds will go towards our outreach and diversity programs: Django Girls workshops, the Django Fellowship program, sponsoring official Django conferences, and others. *Please note this purchase is not a tax-deductible donation. Type Hinting (PEP 484) in Django under the Django Fellowship Program Additionally, the DSF and JetBrains announce a grant for the Django core development activity under the Django Fellowship program, in order to bring the new Python Type Hints standard (PEP 484) into future versions of Django. “Python 3 support has been a strong focus for Django in recent years,” says Wiles. “Python 3.5 and type hinting are a huge step towards developer productivity, especially combined with powerful tools like PyCharm. This JetBrains grant helps our Django Fellows and community bring type hinting to Django.” The standard is already quite stable, with only a few amendments over the last year. With this work, which is starting soon, the DSF will be funding Django core developers and other community members to help with the development. “We believe in Python 3 and the benefits of type hinting, particularly for frameworks like Django,” says Filippov. “Type hints in Django can let PyCharm boost Django developer productivity with better code inspections, code completion, and refactorings. We’re going to pioneer PEP 484 use in Django, making tremendous headway into the future of Django and Python.” There's no exact timeline for the project yet, but keep an eye on the django-developers mailing list and the Django blog for updates as work progresses. If you have any questions, get in touch with us at [email protected] or JetBrains at [email protected]. [Less]

[APIs are an increasingly important part of modern web development, and Django REST Framework makes them super-easy to develop. I know I've found it a super-useful part of my Django toolkit. Tom Christie, the lead developer of Django REST Framework ... [More] , is looking to continue development of Django REST Framework as a full-time job, and to do so he needs our help. I hope you'll consider supporting the project. Now, here's Tom to tell you more: -JKM] Earlier this month I left regular employment, in order to focus completely on the continued development of Django REST framework. In order to make this possible I've launched a funding drive, with the aim of providing a full-time salary. With a number of sponsors already signed up, the campaign is currently over one-third of the way towards its goal. I believe that this is a great opportunity for companies using Django REST framework to help push the Django ecosystem forward. A fully-funded development role would make a major impact on the project, and allow us to rapidly increase the pace of feature development, documentation improvements, and maintenance work. I would urge any companies that use and rely on Django REST framework to sign up for one of the plans, and help secure the project's ongoing success. [Less]

As part of the Django 1.10 release process, today we've released Django 1.10 beta 1, a preview/testing package that represents the second stage in the 1.10 release cycle and an opportunity for you to try out the changes coming in Django 1.10. Django ... [More] 1.10 has a panoply of new features which you can read about in the in-development 1.10 release notes. Only bugs in new features and regressions from earlier versions of Django will be fixed between now and 1.10 final (also, translations will be updated following the "string freeze" when the release candidate is issued). The current release schedule calls for a release candidate about a month from now with the final release to follow about two weeks after that around August 1. We'll only be able to keep this schedule if we get early and often testing from the community. Updates on the release schedule schedule are available on the django-developers mailing list. As with all alpha and beta packages, this is not for production use. But if you'd like to take some of the new features for a spin, or to help find and fix bugs (which should be reported to the issue tracker), you can grab a copy of the beta package from our downloads page or on PyPI. The PGP key ID used for this release is Tim Graham: 1E8ABDC773EDE252. [Less]

Today we've issued a bugfix release for the 1.9 release series. Details can be found in the release notes for 1.9.7. The release package and checksums are available from our downloads page, as well as from the Python Package Index. The PGP key ID used for this release is Tim Graham: 1E8ABDC773EDE252.

As part of the Django 1.10 release process, today we've released Django 1.10 alpha 1, a preview/testing package that represents the first stage in the 1.10 release cycle and an opportunity for you to try out the changes coming in Django 1.10. Django ... [More] 1.10 has a panoply of new features which you can read about in the in-development 1.10 release notes. This alpha milestone marks a complete feature freeze. The current release schedule calls for a beta release in about a month and a release candidate about a month from then. We'll only be able to keep this schedule if we get early and often testing from the community. Updates on the release schedule schedule are available on the django-developers mailing list. As with all alpha and beta packages, this is not for production use. But if you'd like to take some of the new features for a spin, or to help find and fix bugs (which should be reported to the issue tracker), you can grab a copy of the alpha package from our downloads page or on PyPI. The PGP key ID used for this release is Tim Graham: 1E8ABDC773EDE252. [Less]

Today we've issued bugfix releases for the 1.9 and 1.8 release series. Details can be found in the release notes for 1.9.6 and 1.8.13. The release package and checksums are available from our downloads page, as well as from the Python Package Index. The PGP key ID used for this release is Tim Graham: 1E8ABDC773EDE252.