Added new tests for alternate uses for alternate range request types.
Changed error handlnig for new request logic that simplifies the integration logic
Moved the error handler and the content range handler to their own handler file to prevent circular imports.
If we don"t `export` the variable, it's not available in subcommand:
MYAPP_SETTINGS=/path/to/config_file; python3 -c "import os; os.environ['MYAPP_SETTINGS']"
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/python3.5/os.py", line 725, in __getitem__
raise KeyError(key) from None
KeyError: 'MYAPP_SETTINGS'
The ';' is the culprit here.
Blueprints currently queue functions to be called, which are simple, yet
hard to inspect. These changes allow tools to be built that analyze
blueprints more easily.
Added new tests for alternate uses for alternate range request types.
Changed error handlnig for new request logic that simplifies the integration logic
Moved the error handler and the content range handler to their own handler file to prevent circular imports.
Added new tests for alternate uses for alternate range request types.
Changed error handlnig for new request logic that simplifies the integration logic
Moved the error handler and the content range handler to their own handler file to prevent circular imports.
If we don"t `export` the variable, it's not available in subcommand:
MYAPP_SETTINGS=/path/to/config_file; python3 -c "import os; os.environ['MYAPP_SETTINGS']"
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/python3.5/os.py", line 725, in __getitem__
raise KeyError(key) from None
KeyError: 'MYAPP_SETTINGS'
The ';' is the culprit here.
Blueprints currently queue functions to be called, which are simple, yet
hard to inspect. These changes allow tools to be built that analyze
blueprints more easily.
