reserved $whoami • 软件工程师 (1991 – 今) • Python 程序员（2009 – 今） • Evangelist @ （2015 – 今） • System Engineer @ （2011-1025） • Architect Evangelist @ (2004-2011) … Serverless 为何而生 amazon.com/serverless/sam SAM CLI sam init --name my-function --runtime python cd my-function/ sam build sam package --s3-bucket my-packages-bucket \ --output-template-file packaged.yaml sam deploy --template-file

Protecting Runtime Memory Data 2.3. Packing with outer key 2.4. Building obfuscated wheel 2.5. Protecting system packages 2.6. Fix encoding error 2.7. Removing docstring 2.8. Using Pyarmor in CI Pipeline 2.9. Work 3.5.1. Building Errors 3.5.2. Runtime Errors 3.5.3. Outer Errors 3.6. Pyarmor Check List 3.6.1. Build Device 3.6.2. Target Device 3.6.3. Platform Issues 4. Topics 4.1. Insight Into Obfuscation 4.1 old license to Pyarmor Basic 6. FAQ 6.1. Asking questions in GitHub 6.2. Reporting bug 6.2.1. Build issues 6.2.2. Pack issues 6.2.3. Runtime issues 6.3. Hot Questions 6.4. License 6.4.1. Upgrading

programming (OOP), is a way of programming that focuses on using objects and classes to design and build applications.. Major pillars of Object Oriented Programming (OOP) are Inheritance, Polymorphism, Abstraction, ad Encapsulation. Object Oriented Analysis(OOA) is the process of examining a problem, system or task and identifying the objects and interactions between them. Why to Choose Object Oriented Programming (OOP) allows decomposition of a problem into a number of units called objects and then build the data and functions around these objects. It emphasis more on the data than procedure or functions

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 6.7 build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . obfuscated, and use shared runtime files. First change to work path, create 3 projects: mkdir build cd build pyarmor init --src /path/to/pkg1 --entry __init__.py pkg1 pyarmor init --src /path/to/pkg2 --entry the path dist: pyarmor build --output dist --only-runtime pkg1 Next obfuscate 3 packages, save them in the dist: pyarmor build --output dist --no-runtime pkg1 pyarmor build --output dist --no-runtime

Project Project Configuration File Man Page Common Options obfuscate licenses pack hdinfo init config build info check banchmark register download runtime Understanding Obfuscated Scripts Global Capsule obfuscated, and use shared runtime files. First change to work path, create 3 projects: mkdir build cd build pyarmor init --src /path/to/pkg1 --entry __init__.py pkg1 pyarmor init --src /path/to/pkg2 --entry the path dist: pyarmor build --output dist --only-runtime pkg1 Next obfuscate 3 packages, save them in the dist: pyarmor build --output dist --no-runtime pkg1 pyarmor build --output dist --no-runtime

Project Project Configuration File Man Page Common Options obfuscate licenses pack hdinfo init config build info check banchmark register download runtime Understanding Obfuscated Scripts Global Capsule obfuscated, and use shared runtime files. First change to work path, create 3 projects: mkdir build cd build pyarmor init --src /path/to/pkg1 --entry __init__.py pkg1 pyarmor init --src /path/to/pkg2 --entry the path dist: pyarmor build --output dist --only-runtime pkg1 Next obfuscate 3 packages, save them in the dist: pyarmor build --output dist --no-runtime pkg1 pyarmor build --output dist --no-runtime

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 6.8 build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . obfuscated, and use shared runtime files. First change to work path, create 3 projects: mkdir build cd build pyarmor init --src /path/to/pkg1 --entry __init__.py pkg1 pyarmor init --src /path/to/pkg2 --entry the path dist: pyarmor build --output dist --only-runtime pkg1 Next obfuscate 3 packages, save them in the dist: pyarmor build --output dist --no-runtime pkg1 pyarmor build --output dist --no-runtime

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 6.8 build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . obfuscated, and use shared runtime files. First change to work path, create 3 projects: mkdir build cd build pyarmor init --src /path/to/pkg1 --entry __init__.py pkg1 pyarmor init --src /path/to/pkg2 --entry the path dist: pyarmor build --output dist --only-runtime pkg1 Next obfuscate 3 packages, save them in the dist: pyarmor build --output dist --no-runtime pkg1 pyarmor build --output dist --no-runtime

gives full power and flexibility of SQL to an application developer. It is an open source and cross-platform software released under MIT license. SQLAlchemy is famous for its object-relational mapper gives full power and flexibility of SQL to an application developer. It is an open source and cross-platform software released under MIT license. SQLAlchemy is famous for its object-relational mapper data between incompatible type systems in object-oriented programming languages. Usually, the type system used in an Object Oriented (OO) language like Python contains non-scalar types. These cannot be

to allow you to nest command line utilities. The idea is that you can have a system that works together with another system by tacking two click instances together and they will continue working as they Python library that aims to create a level of composability of applications that goes beyond what the system itself supports. Docopt, for instance, acts by parsing your help pages and then parsing according benefit from this. The aim of click is to make composable systems, whereas the aim of docopt is to build the most beautiful and hand- crafted command line interfaces. These two goals conflict with one another