| Age | Commit message (Collapse) | Author |
|
- Describe 'pyproject.toml' usage (replacing 'setup.py', 'pytest.ini',
'.coveragerc').
- Document the new PyPA-blessed build process.
|
|
|
|
|
|
|
|
- Swap order of editing tutorial/views/default.py so that line numbers in the user's editor align with the rendered docs
|
|
|
|
|
|
- See https://github.com/Pylons/pyramid-cookiecutter-starter/pull/66
|
|
align line numbers with code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- minor grammar and reST fixes
|
|
|
|
a footnote from wiki2 example.
|
|
|
|
- trim index
|
|
|
|
- update templates and static assets for new design
|
|
- update templates and static assets to new theme
|
|
Modify `lines` to include closing parens in source and update corresponding `emphasize-lines`. Closes #1606.
|
|
with the same indentation as the rest of the code block)
|
|
remember_userid/forget_userid methods from request
|
|
|
|
The pyramid.security Authorization API function has_permission is made available on the request.
The pyramid.security Authentication API functions are now available as
properties (unauthenticated_userid, authenticated_userid, effective_principals)
and methods (remember_userid, forget_userid) on pyramid.request.Request.
Backwards compatibility:
For each of the APIs moved to request method or property,
the original API in the pyramid.security module proxies to the request.
Reworked tests to check module level b/c wrappers call through to mixins for each API.
Tests that check no reg on request now do the right thing.
Use a response callback to set the request headers for forget_userid and remember_userid.
Update docs.
Attempt to improve a documentation section referencing the pyramid.security.has_permission
function in docs/narr/resources.rst
Ensures backwards compatiblity for `pyramid.security.forget`
and `pyramid.security.remember`.
|
|
Align code in docs with that in the src directory.
|
|
|
|
* This avoids having to update the link multiple times.
* Also, mention their location, in case user has Pyramid checkout.
|
|
- In the Basic Layout and Authorization chapters
of the ZODB wiki tutorial
|
|
AuthTktAuthenticationPolicy now accepts a hashalg parameter and is no
longer deprecated. Docs recommend overriding hashalg and using 'sha512'.
|
|
zope.deprecation instead of a warning, make hashalg arg a kwarg in certain cases in case someone (maybe me) is using nonapi function imports from authentication
|
|
- Normalize the Seeing our changes section
- Changed import to recommended style
|
|
- Sync content of Add login and logout views,
Add the login.pt template, Return a logged_in
flag, Add a logout link sections
- Normalize sections of views.py
|
|
- Sync content in Adding Authentication and
Authorization policies, Add permission
declarations sections
- Added mising permission=view in SQL tutorial
- Moved __init__.py listing to Seeing our changes
|
|
- Sync content of Add users and groups, and
Add an ACL.
- Added yellow highlight to listings in
Seeing our changes, added models.py
|
|
|
|
- Sync the content of the introduction and the
Viewing the Application in a Browser sections
- Sync the section structure
|
|
|
|
wrapper for ``pyramid.Config.configurator.add_view`` which does the right
thing about permissions. It should be preferred over calling ``add_view``
directly with ``context=HTTPForbidden`` as was previously recommended.
- New API: ``pyramid.view.forbidden_view_config``. This is a decorator
constructor like ``pyramid.view.view_config`` that calls
``pyramid.config.Configurator.add_forbidden_view`` when scanned. It should
be preferred over using ``pyramid.view.view_config`` with
``context=HTTPForbidden`` as was previously recommended.
- Updated the "Creating a Not Forbidden View" section of the "Hooks" chapter,
replacing explanations of registering a view using ``add_view`` or
``view_config`` with ones using ``add_forbidden_view`` or
``forbidden_view_config``.
- Updated all tutorials to use ``pyramid.view.forbidden_view_config`` rather
than ``pyramid.view.view_config`` with an HTTPForbidden context.
|
|
|