Type Python in a terminal window:
$ python Python 2.7.2+ (default, Jul 20 2012, 22:15:08)
| The 2015 edition of DjangoCon Europe, the biggest event in the international Django community’s calendar, will be held in Cardiff (Wales) 2nd-7th June. | |
| <http://2015.djangocon.eu> | |
| We’re putting a huge emphasis on diversity and accessibility at this event, to encourage more women and members of other minorities in the field to attend and submit proposals for talks. | |
| <http://2015.djangocon.eu/welcome/diversity/> | |
| <http://2015.djangocon.eu/welcome/accessibility/> | |
| We’ve also taken the unusual step of opening registration only to members of under-represented groups for the first month: <http://2015.djangocon.eu/news/registration-opens/>. |
| Rules for using technical words in documentation | |
| ------------------------------------------------ | |
| There should be one consistent way of rendering any technical word. Please follow these rules: | |
| In general use, simply use the word as if it were any ordinary word, with no capitalisation or | |
| highlighting: "Your placeholder can now be used." | |
| At the start of sentences or titles, capitalise in the usual way: "Placeholder management guide". |
| daniele@Danieles-MacBook:~/afraid-to-commit$ git remote add juan https://github.com/reidrac/afraid-to-commit | |
| daniele@Danieles-MacBook:~/afraid-to-commit$ git merge juan/add-my-name | |
| daniele@Danieles-MacBook:~/afraid-to-commit$ git status | |
| # On branch master | |
| # Changes not staged for commit: | |
| # (use "git add <file>..." to update what will be committed) | |
| # (use "git checkout -- <file>..." to discard changes in working directory) | |
| # | |
| # modified: attendees_and_learners.rst | |
| # |
| .. setting:: LOCALE_PATHS | |
| LOCALE_PATHS | |
| ------------ | |
| Default: ``()`` (Empty tuple) | |
| A tuple of directories where Django looks for translation files. | |
| See :ref:`how-django-discovers-translations`. |
| def test_login_required_on_descendants(self): | |
| # checks that the descendants of a page requiring authorisation also require it | |
| parent_page = create_page("page", "nav_playground.html", "en", published=True, | |
| login_required=True) | |
| create_page("childpage", "nav_playground.html", "en", parent=parent_page, | |
| published=True, login_required=False) | |
| request = self.get_request('/') | |
| response = details(request, '') | |
| self.assertEqual(response.status_code, 302) | |
| self.assertEqual(response['Location'], '%s?next=/en/' % settings.LOGIN_URL) |
| ========================= | |
| How the menu system works | |
| ========================= | |
| Basic concepts | |
| ============== | |
| Registration | |
| ------------ |
| The easiest thing is to explain how you use them: | |
| 1. define an insertion point in your template(s) using | |
| {% insert "my_insertion_point" %} | |
| The {% insert %} templatetag will then get_or_create() the appropriate | |
| Insert in the database | |
| 2. the user visits the Insert in the admin, and adds plug-based |