per page, with , order by , clip by
Results of 1 - 10 of about 219 for there (0.004 sec.)
チケットをトリアージする — Django 6.1 ドキュメント 10046
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » チケットをトリアージする ¶ Django uses Trac for managing the work on the code base. Trac is a community-tended garden of the bugs people have found ... and the features Django has decided to add. As in any garden, sometimes there are weeds to be pulled and sometimes there are flowers and vegetables that need picking. We need your help to sort out one ... nity to keep participating, keep tickets as accurate as possible, and raise issues for discussion on the Django Forum when there is confusion or disagreement. Djangoはコミュニティプロジェクトであり、すべての貢献が役立ちます。 あなた なしではこれを実現 ... することはできません! トリアージのワークフロー ¶ Unfortunately, not all reports in the ticket tracker provide all the required details . A number of tickets have proposed solutions, but those don't necessarily meet all the requirements adheri ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
チケットをトリアージする — Django 6.1 ドキュメント 10046
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » チケットをトリアージする ¶ Django uses Trac for managing the work on the code base. Trac is a community-tended garden of the bugs people have found ... and the features Django has decided to add. As in any garden, sometimes there are weeds to be pulled and sometimes there are flowers and vegetables that need picking. We need your help to sort out one ... nity to keep participating, keep tickets as accurate as possible, and raise issues for discussion on the Django Forum when there is confusion or disagreement. Djangoはコミュニティプロジェクトであり、すべての貢献が役立ちます。 あなた なしではこれを実現 ... することはできません! トリアージのワークフロー ¶ Unfortunately, not all reports in the ticket tracker provide all the required details . A number of tickets have proposed solutions, but those don't necessarily meet all the requirements adheri ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
Submitting contributions — Django 6.1 ドキュメント 9941
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 ... easonably timely fashion. If you don't have time to work on it, either unclaim it or don't claim it in the first place! If there's no sign of progress on a particular claimed ticket for a week or two, another developer may ask you to relinquish the ti ... ting, which is quite helpful. Regardless of the way you submit your work, follow these steps. Make sure your code fulfills the requirements in our contribution checklist . Check the "Has patch" box on the ticket and make sure the "Needs documentation" ... irements. Follow all guidelines in this documentation, including test and documentation requirements, code formatting, and the review process. Follow the GitHub pull request template. Ensure the PR template is present and fully completed, including al ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
Submitting contributions — Django 6.1 ドキュメント 9826
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 ... easonably timely fashion. If you don't have time to work on it, either unclaim it or don't claim it in the first place! If there's no sign of progress on a particular claimed ticket for a week or two, another developer may ask you to relinquish the ti ... ting, which is quite helpful. Regardless of the way you submit your work, follow these steps. Make sure your code fulfills the requirements in our contribution checklist . Check the "Has patch" box on the ticket and make sure the "Needs documentation" ... irements. Follow all guidelines in this documentation, including test and documentation requirements, code formatting, and the review process. Follow the GitHub pull request template. Ensure the PR template is present and fully completed, including al ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
Django 0.95 リリースノート — Django 6.1 ドキュメント 8530
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 0.95 リリースノート ¶ Django 0.95 へようこそ! このリリースでは、2006年1月にリリースされた 0.91 から Django の開発が大幅に進んでいます。このリ ... ou understand APIs may change in the future. Fortunately, most of Django's core APIs won't be changing before version 1.0. There likely won't be as big of a change between 0.95 and 1.0 versions as there was between 0.91 and 0.95. 変更と新機能 ¶ The ma ... ango, prior to its open-source release. It's now possible to write more natural, Pythonic code that works as expected, and there's less "black magic" happening behind the scenes. Aside from that, another main theme of this release is a dramatic increa ... are, for the most part, reasonably routine and only need to be done once. A list of the necessary changes is described in the Removing The Magic wiki page. There is also an easy checklist for reference when undertaking the porting operation. Problem ...
https://man.mtool.work/django/6.1/releases/0.95.html
Django 0.95 リリースノート — Django 6.1 ドキュメント 8415
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 0.95 リリースノート ¶ Django 0.95 へようこそ! このリリースでは、2006年1月にリリースされた 0.91 から Django の開発が大幅に進んでいます。このリ ... ou understand APIs may change in the future. Fortunately, most of Django's core APIs won't be changing before version 1.0. There likely won't be as big of a change between 0.95 and 1.0 versions as there was between 0.91 and 0.95. 変更と新機能 ¶ The ma ... ango, prior to its open-source release. It's now possible to write more natural, Pythonic code that works as expected, and there's less "black magic" happening behind the scenes. Aside from that, another main theme of this release is a dramatic increa ... are, for the most part, reasonably routine and only need to be done once. A list of the necessary changes is described in the Removing The Magic wiki page. There is also an easy checklist for reference when undertaking the porting operation. Problem ...
https://man.mtool.work/django/6.1/releases/0.95.html
Django 1.0 リリースノート — Django 6.1 ドキュメント 8195
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.0 リリースノート ¶ Django 1.0 へようこそ! We've been looking forward to this moment for over three years, and it's finally here. Django 1.0 ... .0 をリリースできたのは、まさにオープンソースとしてふさわしい出来事だと思われます。 Stability and forwards-compatibility ¶ The release of Django 1.0 comes with a promise of API stability and forwards-compatibility. In a nutshell, this means that code ... ed around 350,000 lines of code. We've also added 40,000 lines of new documentation, and greatly improved what was already there. In fact, new documentation is one of our favorite features of Django 1.0, so we might as well start there. First, there's ... site: https://docs.djangoproject.com/ The documentation has been greatly improved, cleaned up, and generally made awesome. There's now dedicated search, indexes, and more. We can't possibly document everything that's new in 1.0, but the documentation ...
https://man.mtool.work/django/6.1/releases/1.0.html
Django 1.0 リリースノート — Django 6.1 ドキュメント 8091
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.0 リリースノート ¶ Django 1.0 へようこそ! We've been looking forward to this moment for over three years, and it's finally here. Django 1.0 ... .0 をリリースできたのは、まさにオープンソースとしてふさわしい出来事だと思われます。 Stability and forwards-compatibility ¶ The release of Django 1.0 comes with a promise of API stability and forwards-compatibility. In a nutshell, this means that code ... ed around 350,000 lines of code. We've also added 40,000 lines of new documentation, and greatly improved what was already there. In fact, new documentation is one of our favorite features of Django 1.0, so we might as well start there. First, there's ... site: https://docs.djangoproject.com/ The documentation has been greatly improved, cleaned up, and generally made awesome. There's now dedicated search, indexes, and more. We can't possibly document everything that's new in 1.0, but the documentation ...
https://man.mtool.work/django/6.1/releases/1.0.html
Django 0.96 リリースノート — Django 6.1 ドキュメント 7652
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 0.96 リリースノート ¶ Django 0.96 へようこそ! The primary goal for 0.96 is a cleanup and stabilization of the features introduced in 0.95. There ... rates for foreign key references have changed slightly. These names are generally only used when it is not possible to put the reference directly on the affected column, so they are not always visible. The effect of this change is that running manage. ... se the database server to raise an error message about modifying nonexistent constraints. If you need to work around this, there are two methods available: Redirect the output of manage.py to a file, and edit the generated SQL to use the correct const ... database. Name changes in manage.py ¶ A few of the options to manage.py have changed with the addition of fixture support: There are new dumpdata and loaddata commands which, as you might expect, will dump and load data to/from the database. These com ...
https://man.mtool.work/django/6.1/releases/0.96.html
Django 1.6 リリースノート — Django 6.1 ドキュメント 7547
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.6 リリースノート ¶ 注釈 Dedicated to Malcolm Tredinnick On March 17, 2013, the Django project and the free software community lost a very d ... nd raises ValueError if undefined order is spotted. The order is seen as undefined if the given QuerySet isn't ordered and there is more than one ordered value to compare against. Added earliest() for symmetry with latest() . In addition to year , mon ... t 's __dict__ . HttpResponseRedirect and HttpResponsePermanentRedirect now provide an url attribute (equivalent to the URL the response will redirect to). The MemcachedCache cache backend now uses the latest pickle protocol available. Added SuccessMes ... choices argument to model fields now accepts an iterable of iterables instead of requiring an iterable of lists or tuples. The reason phrase can be customized in HTTP responses using reason_phrase . When giving the URL of the next page for django.cont ...
https://man.mtool.work/django/6.1/releases/1.6.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT