per page, with , order by , clip by
Results of 1 - 10 of about 62 for sure (0.006 sec.)
How to release Django — Django 6.1 ドキュメント 14088
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up How to release Django ¶ このドキュメントでは、Django のリリース方法について説明しています。 これらの手順を変更した場合は、最新の情報を保ってください! ここでの ... ers and create the release artifacts. Create the new Release in the admin on djangoproject.com . Set the proper date but ensure the flag is_active is disabled. Upload the artifacts (tarball, wheel, and checksums). Verify package(s) signatures, check ... if they can be installed, and ensure minimal functionality. Upload the new version(s) to PyPI. Enable the is_active flag for each release in the admin on djang ... s. Access to Django's project on PyPI to upload binaries, ideally with extra permissions to yank a release if necessary. Ensure your PyPI account only uses WebAuthn-based authentication factors, not TOTP (one-time codes). Create an API token followin ...
https://man.mtool.work/django/6.1/internals/howto-release-django.html
How to release Django — Django 6.1 ドキュメント 13539
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up How to release Django ¶ このドキュメントでは、Django のリリース方法について説明しています。 これらの手順を変更した場合は、最新の情報を保ってください! ここでの ... ers and create the release artifacts. Create the new Release in the admin on djangoproject.com . Set the proper date but ensure the flag is_active is disabled. Upload the artifacts (tarball, wheel, and checksums). Verify package(s) signatures, check ... if they can be installed, and ensure minimal functionality. Upload the new version(s) to PyPI. Enable the is_active flag for each release in the admin on djang ... s. Access to Django's project on PyPI to upload binaries, ideally with extra permissions to yank a release if necessary. Ensure your PyPI account only uses WebAuthn-based authentication factors, not TOTP (one-time codes). Create an API token followin ...
https://man.mtool.work/django/6.1/internals/howto-release-django.html
新しいコントリビューターへのアドバイス — Django 6.1 ドキュメント 9551
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 新しいコントリビューターへのアドバイス ¶ 新しいコントリビューターで、何をするべきかわかりませんか? 助けたいと思っているのにどこから手を付ければいいの ... produce it. If you can reproduce it and it seems valid, make a note that you confirmed the bug and accept the ticket. Make sure the ticket is filed under the correct component area. Consider writing a patch that adds a test for the bug's behavior, ev ... keep an eye out for syntax that is incompatible with older but still supported versions of Python. Run the tests and make sure they pass. Where possible and relevant, try them out on a database other than SQLite. Leave comments and feedback! Keep ol ... tches up-to-date ¶ Oftentimes the codebase will change between a patch being submitted and the 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 Contributio ...
https://man.mtool.work/django/6.1/internals/contributing/new-contributors.html
Submitting contributions — Django 6.1 ドキュメント 8655
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 ... feature is being worked on. If you have identified a contribution you want to make and you're capable of fixing it (as measured by your coding ability, knowledge of Django internals and time availability), claim it by following these steps: Log in u ... uld follow the process for suggesting new features . If a ticket for this issue already exists and has been accepted, make sure nobody else has claimed it. To do this, look at the "Owned by" section of the ticket. If it's assigned to "nobody," then i ... you have the option to sign and submit a Contributor License Agreement clarifying the status of your contribution. This ensures that the Django Software Foundation has clear license to your contribution. Ticket claimers' responsibility ¶ Once you've ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
Submitting contributions — Django 6.1 ドキュメント 8655
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 ... feature is being worked on. If you have identified a contribution you want to make and you're capable of fixing it (as measured by your coding ability, knowledge of Django internals and time availability), claim it by following these steps: Log in u ... uld follow the process for suggesting new features . If a ticket for this issue already exists and has been accepted, make sure nobody else has claimed it. To do this, look at the "Owned by" section of the ticket. If it's assigned to "nobody," then i ... you have the option to sign and submit a Contributor License Agreement clarifying the status of your contribution. This ensures that the Django Software Foundation has clear license to your contribution. Ticket claimers' responsibility ¶ Once you've ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
新しいコントリビューターへのアドバイス — Django 6.1 ドキュメント 8467
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 新しいコントリビューターへのアドバイス ¶ 新しいコントリビューターで、何をするべきかわかりませんか? 助けたいと思っているのにどこから手を付ければいいの ... produce it. If you can reproduce it and it seems valid, make a note that you confirmed the bug and accept the ticket. Make sure the ticket is filed under the correct component area. Consider writing a patch that adds a test for the bug's behavior, ev ... keep an eye out for syntax that is incompatible with older but still supported versions of Python. Run the tests and make sure they pass. Where possible and relevant, try them out on a database other than SQLite. Leave comments and feedback! Keep ol ... tches up-to-date ¶ Oftentimes the codebase will change between a patch being submitted and the 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 Contributio ...
https://man.mtool.work/django/6.1/internals/contributing/new-contributors.html
Django 1.5 リリースノート — Django 6.1 ドキュメント 8467
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.5 リリースノート ¶ February 26, 2013 Django 1.5 へようこそ! These release notes cover the new features , as well as some backwards incompat ... automated test suite, it's received very little real-world testing. We've done our best to eliminate bugs, but we can't be sure we covered all possible uses of Django. Some features of Django aren't available because they depend on third-party softwa ... list_filter() method. Backwards incompatible changes in 1.5 ¶ 警告 In addition to the changes outlined in this section, be sure to review the deprecation plan for any features that have been removed. If you haven't updated your code within the deprec ... s truncated before each test run in a TransactionTestCase . In order to be able to run unit tests in any order and to make sure they are always isolated from each other, TransactionTestCase will now reset the database after each test run instead. No ...
https://man.mtool.work/django/6.1/releases/1.5.html
Django 1.5 リリースノート — Django 6.1 ドキュメント 8467
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.5 リリースノート ¶ February 26, 2013 Django 1.5 へようこそ! These release notes cover the new features , as well as some backwards incompat ... automated test suite, it's received very little real-world testing. We've done our best to eliminate bugs, but we can't be sure we covered all possible uses of Django. Some features of Django aren't available because they depend on third-party softwa ... list_filter() method. Backwards incompatible changes in 1.5 ¶ 警告 In addition to the changes outlined in this section, be sure to review the deprecation plan for any features that have been removed. If you haven't updated your code within the deprec ... s truncated before each test run in a TransactionTestCase . In order to be able to run unit tests in any order and to make sure they are always isolated from each other, TransactionTestCase will now reset the database after each test run instead. No ...
https://man.mtool.work/django/6.1/releases/1.5.html
アクセシビリティ — Django 6.1 ドキュメント 8293
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » アクセシビリティ ¶ The Django project is committed to ensuring that websites built with Django are usable by everyone, including people with disabil ... , a community-driven effort to make digital accessibility easier. サポート対象とテスト ¶ Beyond standards, we want to make sure Django actually works for people using a wide range of input devices and assistive technologies. This has benefits to make ... sure Django works better for everyone . The best way to do this effectively is to take accessibility considerations into accoun ...
https://man.mtool.work/django/6.1/internals/contributing/accessibility.html
アクセシビリティ — Django 6.1 ドキュメント 8293
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » アクセシビリティ ¶ The Django project is committed to ensuring that websites built with Django are usable by everyone, including people with disabil ... , a community-driven effort to make digital accessibility easier. サポート対象とテスト ¶ Beyond standards, we want to make sure Django actually works for people using a wide range of input devices and assistive technologies. This has benefits to make ... sure Django works better for everyone . The best way to do this effectively is to take accessibility considerations into accoun ...
https://man.mtool.work/django/6.1/internals/contributing/accessibility.html
PREV 1 2 3 4 5 6 7 NEXT