per page, with , order by , clip by
Results of 1 - 10 of about 54 for important (0.004 sec.)
Submitting contributions — Django 6.1 ドキュメント 11258
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Submitting contributions ¶ We're always grateful for contributions to Django's code. Indeed, bug reports with associated contributions will get fixe ... to use pull requests. "Claiming" tickets ¶ In an open-source project with hundreds of contributors around the world, it's important to manage communication efficiently so that work doesn't get duplicated and contributors can be as effective as possible. ... on is required when a patch introduces new Django functionality and makes some sort of design decision. This is especially important if the approach involves a deprecation or introduces breaking changes. The following are different approaches for gaining ... nDjangoXXXXWarning , msg ) as ctx : # invoke deprecated behavior ... self . assertEqual ( ctx . filename , __file__ ) It's important to include a RemovedInDjangoXXXXWarning comment above code which has no warning reference, but will need to be changed or ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
Submitting contributions — Django 6.1 ドキュメント 11258
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Submitting contributions ¶ We're always grateful for contributions to Django's code. Indeed, bug reports with associated contributions will get fixe ... to use pull requests. "Claiming" tickets ¶ In an open-source project with hundreds of contributors around the world, it's important to manage communication efficiently so that work doesn't get duplicated and contributors can be as effective as possible. ... on is required when a patch introduces new Django functionality and makes some sort of design decision. This is especially important if the approach involves a deprecation or introduces breaking changes. The following are different approaches for gaining ... nDjangoXXXXWarning , msg ) as ctx : # invoke deprecated behavior ... self . assertEqual ( ctx . filename , __file__ ) It's important to include a RemovedInDjangoXXXXWarning comment above code which has no warning reference, but will need to be changed or ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
バグレポートと機能のリクエスト — Django 6.1 ドキュメント 10517
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » バグレポートと機能のリクエスト ¶ 重要 Please report security issues only to security@djangoproject.com . This is a private list only open to long-ti ... This is where the community and the Steering Council evaluate new ideas for the Django ecosystem. This step is especially important for large or complex proposals. We prefer to discuss any significant changes to Django's core before any development begin ... he final release, ensuring a smoother upgrade experience for everyone. Prerequisites ¶ Before testing a pre-release, it is important that your project is running smoothly on the latest stable release of Django. That way, any regressions can be attributed ... -release version. Test manually: While automated tests are great, manually testing your application's main workflows is an important part of verifying compatibility with a new release. Reporting issues ¶ If you discover a bug, please report it via the Dja ...
https://man.mtool.work/django/6.1/internals/contributing/bugs-and-features.html
バグレポートと機能のリクエスト — Django 6.1 ドキュメント 10517
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » バグレポートと機能のリクエスト ¶ 重要 Please report security issues only to security@djangoproject.com . This is a private list only open to long-ti ... This is where the community and the Steering Council evaluate new ideas for the Django ecosystem. This step is especially important for large or complex proposals. We prefer to discuss any significant changes to Django's core before any development begin ... he final release, ensuring a smoother upgrade experience for everyone. Prerequisites ¶ Before testing a pre-release, it is important that your project is running smoothly on the latest stable release of Django. That way, any regressions can be attributed ... -release version. Test manually: While automated tests are great, manually testing your application's main workflows is an important part of verifying compatibility with a new release. Reporting issues ¶ If you discover a bug, please report it via the Dja ...
https://man.mtool.work/django/6.1/internals/contributing/bugs-and-features.html
Django 1.2 リリースノート — Django 6.1 ドキュメント 10146
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.2 リリースノート ¶ 2010 年 5 月 17 日 Django 1.2 へようこそ! Nearly a year in the making, Django 1.2 packs an impressive list of new featur ... es and lots of bug fixes. These release notes cover the new features, as well as important changes you'll want to be aware of when upgrading from Django 1.1 or older versions. オーバービュー ¶ Django 1.2 introduce ... s several large, important new features, including: Support for multiple database connections in a single Django instance. Model validation inspired ... cted until the old system is removed in Django 1.4. However, upgrading to the new CSRF protection framework requires a few important backwards-incompatible changes, detailed in CSRF Protection , below. Authors of custom Field subclasses should be aware th ...
https://man.mtool.work/django/6.1/releases/1.2.html
Contributing code — Django 6.1 ドキュメント 9775
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Contributing code ¶ So you'd like to write some code, documentation or tests to improve Django? There are several ways you can help Django's develop ... d behavior How to write and run tests How to run Django's unit tests How to work with Git and GitHub Related topics ¶ It's important to understand how we work and the conventions we adopt. Coding style JavaScript code アクセシビリティ コードのコミット We ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/
Contributing code — Django 6.1 ドキュメント 9404
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Contributing code ¶ So you'd like to write some code, documentation or tests to improve Django? There are several ways you can help Django's develop ... d behavior How to write and run tests How to run Django's unit tests How to work with Git and GitHub Related topics ¶ It's important to understand how we work and the conventions we adopt. Coding style JavaScript code アクセシビリティ コードのコミット We ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/
新しいコントリビューターへのアドバイス — Django 6.1 ドキュメント 9033
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 新しいコントリビューターへのアドバイス ¶ 新しいコントリビューターで、何をするべきかわかりませんか? 助けたいと思っているのにどこから手を付ければいいの ... e time it gets reviewed. Make sure it still applies cleanly and functions as expected. Updating a patch is both useful and important! See more on Contribution checklist . Write some documentation ¶ Django's documentation is great but it can always be impr ... dn't find any existing tests of this feature" don't carry much weight. While it may be true, that means you have the extra-important job of writing the very first tests for that feature, not that you get a pass from writing tests altogether. Be patient ¶ ...
https://man.mtool.work/django/6.1/internals/contributing/new-contributors.html
Django 1.2 リリースノート — Django 6.1 ドキュメント 9033
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.2 リリースノート ¶ 2010 年 5 月 17 日 Django 1.2 へようこそ! Nearly a year in the making, Django 1.2 packs an impressive list of new featur ... es and lots of bug fixes. These release notes cover the new features, as well as important changes you'll want to be aware of when upgrading from Django 1.1 or older versions. オーバービュー ¶ Django 1.2 introduce ... s several large, important new features, including: Support for multiple database connections in a single Django instance. Model validation inspired ... cted until the old system is removed in Django 1.4. However, upgrading to the new CSRF protection framework requires a few important backwards-incompatible changes, detailed in CSRF Protection , below. Authors of custom Field subclasses should be aware th ...
https://man.mtool.work/django/6.1/releases/1.2.html
新しいコントリビューターへのアドバイス — Django 6.1 ドキュメント 9033
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 新しいコントリビューターへのアドバイス ¶ 新しいコントリビューターで、何をするべきかわかりませんか? 助けたいと思っているのにどこから手を付ければいいの ... e time it gets reviewed. Make sure it still applies cleanly and functions as expected. Updating a patch is both useful and important! See more on Contribution checklist . Write some documentation ¶ Django's documentation is great but it can always be impr ... dn't find any existing tests of this feature" don't carry much weight. While it may be true, that means you have the extra-important job of writing the very first tests for that feature, not that you get a pass from writing tests altogether. Be patient ¶ ...
https://man.mtool.work/django/6.1/internals/contributing/new-contributors.html
PREV 1 2 3 4 5 6 NEXT