ikan Uploader :
Directory : /usr/lib/python3/dist-packages/awscli/customizations/
Upload File : |
| Current File : //usr/lib/python3/dist-packages/awscli/customizations/__init__.py |
# Copyright 2012-2013 Amazon.com, Inc. or its affiliates. All Rights Reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License"). You
# may not use this file except in compliance with the License. A copy of
# the License is located at
#
# http://aws.amazon.com/apache2.0/
#
# or in the "license" file accompanying this file. This file is
# distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF
# ANY KIND, either express or implied. See the License for the specific
# language governing permissions and limitations under the License.
"""
Customizations
==============
As we start to accumulate more and more of these *built-in* customizations
we probably need to come up with some way to organize them and to make
it easy to add them and register them.
One idea I had was to place them all with a package like this. That
at least keeps them all in one place. Each module in this package
should contain a single customization (I think).
To take it a step further, we could have each module define a couple
of well-defined attributes:
* ``EVENT`` would be a string containing the event that this customization
needs to be registered with. Or, perhaps this should be a list of
events?
* ``handler`` is a callable that will be registered as the handler
for the event.
Using a convention like this, we could perhaps automatically discover
all customizations and register them without having to manually edit
``handlers.py`` each time.
"""
Kontol Shell Bypass