Pycon 2012 What Python can learn from Java


Published on

Published in: Technology
1 Comment
  • Please correct the title from 'What Java can learn from Python' to 'What Python can learn from Java'...
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Pycon 2012 What Python can learn from Java

  1. 1. What Python can learn from JavaJonathan Ellis / @spycedPycon 2012
  2. 2. (Not a web development perspective)
  3. 3. The power of tools
  4. 4. Remote debugging✤ -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044✤ 11 steps: “(6) install Wing IDE on the machine on which you plan to run your debug program... (8) copy into the same directory as your source files and import it in your Python source ... (10) In on your debug host, set kWingHostPort ... try setting kLogFile variable in for log additional diagnostic information.”
  5. 5. JMX
  6. 6. Triton
  7. 7. GC in a nutshell✤ Mark✤ Sweep✤ Compact
  8. 8. Aside: reference counting✤ Only good when allocation + assignment are relatively infrequent operations
  9. 9. In short✤ Python has a terrible GC story✤ Poor instrumentation makes it worse
  10. 10. Troubleshooting OOM
  11. 11. Runtime profiling✤✤✤ Commercial: AppDynamics, DynaTrace, others
  12. 12. Building blocks✤ -javaagent✤ ASM:
  13. 13. heapy
  14. 14. Collections✤ Less one-size-fits-all the more you care about performance ✤ HashMap ✤ ImmutableMap ✤ ImmutableSortedMap ✤ TreeMap ✤ ConcurrentSkipListMap ✤ ConcurrentLinkedHashMap ✤ SnapTreeMap ✤ NonBlockingHashMap✤ Not to mention BiMap, Multimap, ...
  15. 15. Lists?✤ ArrayList✤ CopyOnWriteArrayList✤ ArrayBlockingDeque✤ LinkedBlockingDeque✤ PriorityQueue, PriorityBlockingQueue✤ SynchronousQueue✤ TransferQueue (Java7)
  16. 16. Where are these in Python?✤ Python developers want to write Python, not C✤ Similar question: “Why not Cassandra in Python?”✤ PyPy to the rescue? ✤ RPython extension methods
  17. 17. Growing a language (1998)✤ Guy Steele: “I should not design a small language, and I should not design a large one. I need to design a language that can grow.” ✤✤ Currently, Python is not a growable language
  18. 18. Concurrency✤ ExecutorService, ThreadPoolExecutor ✤ FutureTask ✤ Also: ScheduledThreadPoolExecutor✤ ForkJoinPool
  19. 19. Concurrency✤ For CPU-bound applications, copies are the enemy ✤ Useful but dangerous: ✤ List.subList, NavigableMap.subMap✤ Corollary: you need to support threads + shared state ✤ Twisted ✤ Actor model ✤ Multi-process + sysv✤ Local and remote computation: one size does not fit all
  20. 20. Copies are bad✤ Copies of large things are especially bad ✤ Remember fragmentation?✤ Iterators (generators) are good ✤ Java: ByteBuffer ✤ Python: memoryview
  21. 21. The GIL✤ The GIL offers negligible help writing concurrent code✤ Consider this trivial race condition: if d[k] == v1: d[k] = v2
  22. 22. More subtle problems✤ Which of these is threadsafe? ✤ L.append(x) ✤ x = x + 1 ✤ x += 1
  23. 23. More subtle problems✤ Which of these is threadsafe? ✤ L.append(x) ✤ x = x + 1 ✤ x += 1✤ “The thread safety of python operations depends on the compilation of python statements into byte-codes, which is an implementation detail and should not be relied upon.”
  24. 24. Are we stuck with explicit locks?✤ ConcurrentMap ✤ boolean replace(key, oldValue, newValue) ✤ NonBlockingHashMap✤ BlockingQueue✤ CopyOnWriteArrayList
  25. 25. Shared state good, Mutable state bad✤ final: most under-appreciated language feature?✤ guava: Immutable collections ✤✤ Persistent collections ✤ (More accurately, “What Python can learn from Haskell”) ✤ ✤ SnapTreeMap
  26. 26. Final thoughts✤ JRuby is the most advanced Ruby implementation✤ Jython is less popular, but I’d rather write Java than C✤ Once you can write Python libraries that rival native ones for speed, things will get much more interesting