21. A Workshop on Python at NIST
SPAM 1 - First PyCon - Topics
I've assembled a strawman list of topics for discussion. New topics
and comments on the topics listed are certainly welcome.
1. Requirements for a "Safe" Python interpreter
2. A standard GUI module interface definition for Python
3. The requirements for persistent objects in Python
4. A Python engineering graphs package
5. The standard Python WWW interface
6. Embedding Python in a WWW client
7. Technical information management using Python
8. Support for dynamic loading of foreign language modules in Python
9. Replacing make, rcs, and cvs with Python
10.An Electronic Data Interchange library for Python
11.Discussing the formation of a Python Consortium
25. • RestrictedPython
(https://github.com/zopefoundation/RestrictedPython)
• Persistence & persistent
(https://github.com/zopefoundation/Persistence)
(https://github.com/zopefoundation/persistent)
• ZODB (Z Object Database)
https://github.com/zopefoundation/ZODB)
A few Elements of
Bobo / Zope
1998
27. A Workshop on Python at NIST
SPAM 1 - First PyCon - Topics
I've assembled a strawman list of topics for discussion. New topics
and comments on the topics listed are certainly welcome.
1. Requirements for a "Safe" Python interpreter
2. A standard GUI module interface definition for Python
3. The requirements for persistent objects in Python
4. A Python engineering graphs package
5. The standard Python WWW interface
6. Embedding Python in a WWW client
7. Technical information management using Python
8. Support for dynamic loading of foreign language modules in Python
9. Replacing make, rcs, and cvs with Python
10.An Electronic Data Interchange library for Python
11.Discussing the formation of a Python Consortium
28. Digital Creations, L.C.
later became
Zope Corporation
Employees
• Jim Fulton
• Paul Everitt
• Tres Seaver
• Chris McDonough
• Guido van Rossum
• Barry Warsaw
• Jeremy Hylton
• Fred Drake
• Tim Peters
• ...
33. A Workshop on Python at NIST
SPAM 1 - First PyCon - Topics
I've assembled a strawman list of topics for discussion. New topics
and comments on the topics listed are certainly welcome.
1. Requirements for a "Safe" Python interpreter
2. A standard GUI module interface definition for Python
3. The requirements for persistent objects in Python
4. A Python engineering graphs package
5. The standard Python WWW interface
6. Embedding Python in a WWW client
7. Technical information management using Python
8. Support for dynamic loading of foreign language modules in Python
9. Replacing make, rcs, and cvs with Python
10.An Electronic Data Interchange library for Python
11.Discussing the formation of a Python Consortium
First Board of Directors
Python Software Foundation
March 5, 2001 - IPC9
• Greg Stein
• Paul Everitt
47. Lessons Learned
The Good & The Bad
We have learned from our mistakes,
and we keep our users and developers in mind
48. >>> import this
The Zen of Python, by Tim Peters
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to
break the rules.
…
PEP 20 - 19. Aug. 2004 https://www.python.org/dev/peps/pep-0020/
PEP 1 - 13. Jun 2000 / PEP 8 - 5 July 2001
49. Philip J. Eby - Python Core Developer - Author PEP 333/3333 - WSGI
„Those who do not study
Zope, are condemned to
reinvent it.“
50. A Workshop on Python at NIST
SPAM 1 - First PyCon - Topics
I've assembled a strawman list of topics for discussion. New topics
and comments on the topics listed are certainly welcome.
1. Requirements for a "Safe" Python interpreter
2. A standard GUI module interface definition for Python
3. The requirements for persistent objects in Python
4. A Python engineering graphs package
5. The standard Python WWW interface
6. Embedding Python in a WWW client
7. Technical information management using Python
8. Support for dynamic loading of foreign language modules in Python
9. Replacing make, rcs, and cvs with Python
10.An Electronic Data Interchange library for Python
11.Discussing the formation of a Python Consortium
54. Plone Security
„Security is not a state it is a process“
Standing on the shoulders of giants
• Zope Security Architecture
• Fine grained permission system
• RestrictedPython and AccessControl
• Software Design Process
• Skeletons & Code Generators
• Configuration of most aspects
• Permission and Security inheritance
• Most OWASP Vectors did not apply
• Long Security Cycles (5-7 Year per Mayer Version)
55. John Gall - Systemantics: How Systems Really Work and How They Fail
A complex system that works is invariably
found to have evolved from a simple system
that worked. A complex system designed from
scratch never works and cannot be patched up to
make it work. You have to start over with
a working simple system.
CC3-BY-SA https://en.wikipedia.org/wiki/File:Tokyo_by_night_2011.jpg