Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add execution policy to pyramid request processing diagrams #2993

Merged
merged 1 commit into from
Apr 10, 2017

Conversation

stevepiercy
Copy link
Member

No description provided.

@stevepiercy stevepiercy requested a review from mmerickel April 10, 2017 09:42
@piotr-dobrogost
Copy link

It is really nice to have this diagram. I wonder if placing name of current stage of processing in the request object would have any use?

Copy link
Member

@mmerickel mmerickel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mmerickel mmerickel merged commit 3879931 into Pylons:master Apr 10, 2017
@stevepiercy
Copy link
Member Author

@piotr-dobrogost perhaps. Can you describe a specific example?

The diagram is pretty dense as it is. If there were to be any additional information presented, I would have to research ways of including tool tips or raw HTML with Sphinx.

@piotr-dobrogost
Copy link

piotr-dobrogost commented Apr 10, 2017

Well, I was talking about changes in source code not diagram. What I had in mind is on start of each phase of processing shown on the diagram to tag request object with a name of the phase. This would allow to inspect current phase when for example exception in thrown. In other words this would allow to map any place in source code with the specific phase from the diagram.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants