[pypy-commit] extradoc extradoc: some changes to pypy abstract for pyconza, added progress file for august (py3.5)

[plan_rich]

Author: Richard Plangger <planrichi at gmail.com>
Branch: extradoc
Changeset: r5668:3c35a2b9d370
Date: 2016-08-16 08:47 +0200
http://bitbucket.org/pypy/extradoc/changeset/3c35a2b9d370/

Log:	some changes to pypy abstract for pyconza, added progress file for
	august (py3.5)

diff --git a/planning/py3.5/2016-august-progress.rst b/planning/py3.5/2016-august-progress.rst
new file mode 100644
--- /dev/null
+++ b/planning/py3.5/2016-august-progress.rst
@@ -0,0 +1,10 @@
+August 2016
+===========
+
+Planned
+-------
+
+* Implement changes to memory view. e.g. hex(): https://bugs.python.org/issue9951 (plan_rich)
+
+Finished
+--------
diff --git a/talk/pyconza2016/pypy-abstract.txt b/talk/pyconza2016/pypy-abstract.txt
--- a/talk/pyconza2016/pypy-abstract.txt
+++ b/talk/pyconza2016/pypy-abstract.txt
@@ -3,36 +3,16 @@
 
 In this talk I want to show how you can use PyPy for your benefit.
 It will kick off with a short introduction covering PyPy and its just in time
-compiler. PyPy is the most advanced Python interpreter around (besides CPython)
-XXX
-XXX you seem to say "CPython is more advanced than PyPy" above,
-XXX which doesn't make sense in this sentence because you say
-XXX below that PyPy is much faster than CPython
-XXX
+compiler. PyPy is the most advanced Python interpreter around
 and while it should generally just speed up your programs there is a wide range
 of performance that you can get out of PyPy.
 
 The first part, will cover considerations why one should write Python programs,
 and only spend fractions of the development time to optimize your program.
-XXX
-XXX you mean, you want to explain that developers should write in Python
-XXX and spend only a small part of their time optimizing the program?
-XXX or something else?  if I'm right then you should add below something 
-XXX like "The second part of this session will be about this small part
-XXX of time: in cases where you need it, then I'll show tools that..."
-XXX But I'm not sure that's what you mean because CFFI is not really
-XXX about that: I'm trying to push it as a general solution also for
-XXX CPython, without focusing too much on performance.  Maybe we should
-XXX have this talk be really about PyPy, and then for the other talk
-XXX I should have both CFFI and RevDB?
-XXX
-The second part of this session will show and give you the knowledge and
-tools to inspect and change your program to improve it. We will cover two tools in detail:
-CFFI & VMProf.
-
-Our advanced library CFFI (C Foreign Function Interface) can easily replace
-CPython extension code. VMProf is a platform to inspect you program while it is running,
-imposing very little overhead.
+The second part of this session will be about this small part
+of time: in cases where you need it, then I'll show tools that help you inspect
+and change your program to improve it. We will also dive into one tool more elaboratly.
+VMProf, a platform to inspect your program while it is running, imposing very little overhead.
 
 Throughout the talk real world examples will motivate why PyPy is a viable option
 to optimize you Python programs and present the examples' value to their developers.