"uwsgi_modifier1 30" does not work with python3 #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
modifier1 30 has been a (working) hack i would like to remove. Before merging it, can you try using the more 'consistent' --manage-script-name option (you need to remove SCRIPT_NAME handling from nginx) |
|
I thought "--manage-script-name" and "uwsgi_modifier1 30" are both supported features, so I wrote this patch. But now I realized that "uwsgi_modifer1 30" is an obsoleted feature. "--manage-script-name" works without any problems with python2 or python3. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed that "uwsgi_modifer1 30" does not work with python3.
Because environ keys and values are unicode strings.
Please check the changes.