This website requires JavaScript.
Explore
Cloud
Chat
CI/CD
Help
Sign In
maxmustermann
/
pulumi
Watch
1
Star
0
Fork
You've already forked pulumi
0
Code
Issues
Pull requests
Projects
Releases
Wiki
Activity
f59931d242
pulumi
/
sdk
/
python
/
requirements.txt
5 lines
54 B
Plaintext
Raw
Normal View
History
Unescape
Escape
Implement more of the Python runtime This change includes a lot more functionality. Enough to actually run the webserver-py example through previews, updates, and destroys! * Actually wire up the gRPC connections to the engine/monitor. * Move the Node.js and Python generated Protobuf/gRPC files underneath the actual SDK directories to simplify this generally. No more copying during `make` and, in fact, this was required to give a smoother experience with good packages/modules for the Python's SDK development. * Build the Python egg during `make build`. * Add support for program stacks. Just like with the Node.js runtime, we will auto-parent any resources without explicit parents to a single top-level resource component. * Add support for component resource output properties. * Add get_project() and get_stack() functions for retrieving the current project and stack names. * Properly use UNKNOWN sentinels. * Add a set_outputs() function on Resource. This is defined by the code-generator and allows custom logic for output property setting. This is cleaner than the way we do this in Node.js, and gives us a way to ensure that output properties are "real" properties, complete with member documentation. This also gives us a hook to perform name demangling, which the code-generator typically controls anyway. * Add package dependencies to setuptools.py and requirements.txt.
2018-02-24 02:22:26 +01:00
google==2.0.1
grpcio==1.9.1
Use a newer pylint This ensures the new exclusion syntax is accepted, which is required to ignore the Protobuf-generated files which have numerous lint warnings.
2018-02-24 18:34:34 +01:00
pylint==1.8.2
Implement more of the Python runtime This change includes a lot more functionality. Enough to actually run the webserver-py example through previews, updates, and destroys! * Actually wire up the gRPC connections to the engine/monitor. * Move the Node.js and Python generated Protobuf/gRPC files underneath the actual SDK directories to simplify this generally. No more copying during `make` and, in fact, this was required to give a smoother experience with good packages/modules for the Python's SDK development. * Build the Python egg during `make build`. * Add support for program stacks. Just like with the Node.js runtime, we will auto-parent any resources without explicit parents to a single top-level resource component. * Add support for component resource output properties. * Add get_project() and get_stack() functions for retrieving the current project and stack names. * Properly use UNKNOWN sentinels. * Add a set_outputs() function on Resource. This is defined by the code-generator and allows custom logic for output property setting. This is cleaner than the way we do this in Node.js, and gives us a way to ensure that output properties are "real" properties, complete with member documentation. This also gives us a hook to perform name demangling, which the code-generator typically controls anyway. * Add package dependencies to setuptools.py and requirements.txt.
2018-02-24 02:22:26 +01:00
six==1.11.0
Reference in a new issue
Copy permalink