Hi, please find enclosed the Minimal Python Sprint announcement. I post on pypy-dev first to get some feedback before sending it off to other lists... ------------------------------------------------------ Code Sprint towards Minimal Python 17th-23rd Feb. 2003 ------------------------------------------------------ Everybody is invited to join our first Minimal Python Marathon Or was it PyPython? Nevermind. We will have one or - if needed - two big rooms, beamers for presentations (and movies?), a kitchen, internet and a piano. There is a big park and some forest in case you need some fresh air. Short Ad-Hoc presentations about your area of interest, project or plain code will certainly be appreciated. ------------------------------------------------------ Goals of the first Minimal PyPython Marathon ------------------------------------------------------ - codify some ideas that were recently discussed on the pypy-dev codespeak list. - port your favorite C-module to Python (and maintain it :-) - build & enhance infrastructure (python build system, webapps, email, subversion/cvs, automated testing, ...) - rebuild the CPython-Python interpreter in simple Python, running on a minimal "transitive closure" of/in CPython. - try to write platform dependent Assembler/C-code that enables doing C/Machine-level calls from Python without extra C-bindings. - settle on concepts - focus on having some usable results at the end - have a lot of fun meeting like minded people. ------------------------------------------------------ Current Basic Agreements ------------------------------------------------------ Please note, that we have reached some agreement on a number of basic points: a) the Python language is not to be modified. b) simplicity wins. especially against optimization. c) if in doubt we follow the CPython/PEP lead. d) CPython core abstractions are to be cleanly formulated in simple Python. e) Macro-techniques may be used at some levels if there really is no good way to avoid them. But a) to c) still hold. f) our Pythonic core "specification" is intended to be used for all kinds of generational steps e.g to C, Bytecode, Objective-C, assembler and last-but-not-least PSYCO-Specialization. g) if in doubt we follow Armins and Christians lead regarding the right abstraction levels. And any other python people taking responsibility :-) h) there are a lot of wishes, code, thoughts, suggestions and ... names :-) ------------------------------------------------------ How to proceed if you are interested ------------------------------------------------------ If you are interested to come - even parttime - then please subscribe at http://codespeak.net/mailman/listinfo/pypy-sprint where organisational stuff will be communicated. Code- related discussions still take place on the pypy-dev list. For people who don't want or can't spend the money for external rooms i can probably arrange something but it will not be luxurious. btw, there are already five people who will come among them - you guessed it - Christian Tismer and Armin Rigo. ------------------------------------------------------ Disclaimer ------------------------------------------------------ There is no explicit commercial intention behind the organisation of the sprint. On the implicit hand socializing with like-minded people tends to bring up future opportunities. Especially if it's free codespeak ... ups :-) cheers, holger