Andrew Cooke | Contents | Latest | RSS | Previous | Next

C[omp]ute

Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Choochoo Training Diary

Last 100 entries

Surprise Paradox; [Books] Good Author List; [Computing] Efficient queries with grouping in Postgres; [Computing] Automatic Wake (Linux); [Computing] AWS CDK Aspects in Go; [Bike] Adidas Gravel Shoes; [Computing, Horror] Biological Chips; [Books] Weird Lit Recs; [Covid] Extended SIR Models; [Art] York-based Printmaker; [Physics] Quantum Transitions are not Instantaneous; [Computing] AI and Drum Machines; [Computing] Probabilities, Stopping Times, Martingales; bpftrace Intro Article; [Computing] Starlab Systems - Linux Laptops; [Computing] Extended Berkeley Packet Filter; [Green] Mainspring Linear Generator; Better Approach; Rummikub Solver; Chilean Poetry; Felicitations - Empowerment Grant; [Bike] Fixing Spyre Brakes (That Need Constant Adjustment); [Computing, Music] Raspberry Pi Media (Audio) Streamer; [Computing] Amazing Hack To Embed DSL In Python; [Bike] Ruta Del Condor (El Alfalfal); [Bike] Estimating Power On Climbs; [Computing] Applying Azure B2C Authentication To Function Apps; [Bike] Gearing On The Back Of An Envelope; [Computing] Okular and Postscript in OpenSuse; There's a fix!; [Computing] Fail2Ban on OpenSuse Leap 15.3 (NFTables); [Cycling, Computing] Power Calculation and Brakes; [Hardware, Computing] Amazing Pockit Computer; Bullying; How I Am - 3 Years Post Accident, 8+ Years With MS; [USA Politics] In America's Uncivil War Republicans Are The Aggressors; [Programming] Selenium and Python; Better Walking Data; [Bike] How Fast Before Walking More Efficient Than Cycling?; [COVID] Coronavirus And Cycling; [Programming] Docker on OpenSuse; Cadence v Speed; [Bike] Gearing For Real Cyclists; [Programming] React plotting - visx; [Programming] React Leaflet; AliExpress Independent Sellers; Applebaum - Twilight of Democracy; [Politics] Back + US Elections; [Programming,Exercise] Simple Timer Script; [News] 2019: The year revolt went global; [Politics] The world's most-surveilled cities; [Bike] Hope Freehub; [Restaurant] Mama Chau's (Chinese, Providencia); [Politics] Brexit Podcast; [Diary] Pneumonia; [Politics] Britain's Reichstag Fire moment; install cairo; [Programming] GCC Sanitizer Flags; [GPU, Programming] Per-Thread Program Counters; My Bike Accident - Looking Back One Year; [Python] Geographic heights are incredibly easy!; [Cooking] Cookie Recipe; Efficient, Simple, Directed Maximisation of Noisy Function; And for argparse; Bash Completion in Python; [Computing] Configuring Github Jekyll Locally; [Maths, Link] The Napkin Project; You can Masquerade in Firewalld; [Bike] Servicing Budget (Spring) Forks; [Crypto] CIA Internet Comms Failure; [Python] Cute Rate Limiting API; [Causality] Judea Pearl Lecture; [Security, Computing] Chinese Hardware Hack Of Supermicro Boards; SQLAlchemy Joined Table Inheritance and Delete Cascade; [Translation] The Club; [Computing] Super Potato Bruh; [Computing] Extending Jupyter; Further HRM Details; [Computing, Bike] Activities in ch2; [Books, Link] Modern Japanese Lit; What ended up there; [Link, Book] Logic Book; Update - Garmin Express / Connect; Garmin Forerunner 35 v 230; [Link, Politics, Internet] Government Trolls; [Link, Politics] Why identity politics benefits the right more than the left; SSH Forwarding; A Specification For Repeating Events; A Fight for the Soul of Science; [Science, Book, Link] Lost In Math; OpenSuse Leap 15 Network Fixes; Update; [Book] Galileo's Middle Finger; [Bike] Chinese Carbon Rims; [Bike] Servicing Shimano XT Front Hub HB-M8010; [Bike] Aliexpress Cycling Tops; [Computing] Change to ssh handling of multiple identities?; [Bike] Endura Hummvee Lite II; [Computing] Marble Based Logic; [Link, Politics] Sanity Check For Nuclear Launch; [Link, Science] Entropy and Life

© 2006-2017 Andrew Cooke (site) / post authors (content).

Dynamic Dispatch in Python

From: andrew cooke <andrew@...>

Date: Mon, 9 May 2011 17:51:36 -0400

This is an example of how the pytyp type library can be useful.  It's a piece
of code from another part of the pytyp library that rewrites JSON data as
Python classes.

IMPORTANT: I don't expect anyone to understand the code below.  That's not the
point!  Please read on to see what the point is...

The code below is a complex function.  It contains a lot of logic for how to
rewrite different JSON objects.  Lists, for example, should be kept as lists,
but we need to rewrite the contents of the lists (so this rewriting function
needs to call itself recursively).

Hash maps (dicts), however, may be rewritten as Python classes.  That's the
"useful" part of this particular library - it simplifies Python code that
works with JSON.  So when this function finds a dict it needs to compare it
with the specification that the user has entered and do something useful (in
simple terms you can say to the routine "at this point in the JSON data,
convert the data into a class Foo", for example).

Hang on - we're almost at the clever bit...

So this is a complicated function that has to do different things when working
on different types.  Typically in Python you handle a case like this by having
a set of subclasses that all implement the same interface.  And then the
correct action is taken when you call the method on a certain instance.

That's normal OO dispatch - you're chosing a particular method based on the
type of an object.

What pytyp adds here is the ability to dispatch on other function arguments,
instead of "the object before the dot".  So in the call:

   my_function(bar, baz)

you can call different functions depending on the type of baz!  For example:

  my_function(bar, 2)  =>  my_int_function(bar, 2)

  my_function(bar, 'two')  =>  my_str_function(bar, 'two')

When that's applied to this complicated function used to rewrite JSON it lets
us separate out the "routing", which depends on the type of the data, so that
different types are handled by different methods:


  class Transcode:

      @overload
      def __call__(self, value, spec):
	  if isinstance(value, spec):
	      return value
	  else:
	      type_error(value, spec)

      @__call__.intercept
      def map_instance(self, value:Mapping, spec:Sub(Ins)):
	  (varargs, varkw, dict_spec) = class_to_dict_spec(spec)
	  new_value = transcode(value, dict_spec)
	  args = new_value.pop(Rec.OptKey(varargs), []) if varargs else []
	  kargs = new_value.pop(Rec.OptKey(varkw), {}) if varkw else {}
	  args.extend(new_value.pop(index) 
		      for index in sorted(key 
			  for key in new_value.keys() 
			  if isinstance(Rec.OptKey.unpack(key), int)))
	  kargs.update((Rec.OptKey.unpack(key), value) 
		       for (key, value) in new_value.items())    
	  return spec._abc_class(*args, **kargs)

      @__call__.intercept
      def other_instance(self, value, spec:Sub(Ins)):
	  if isinstance(value, spec):
	      return value
	  else:
	      type_error(value, spec)

      @__call__.intercept
      def sequence(self, value, spec:Sub(Seq)):
	  return list(spec._for_each(value, lambda c, vsn: (transcode(v, s) for (v, s, n) in vsn)))

      @__call__.intercept
      def record(self, value, spec:Sub(Rec)):
	  if spec._int_keys():
	      return tuple(spec._for_each(value, 
			  lambda c, vsn: (transcode(v, s) 
					  for (v, s, n) in sorted(vsn, 
					      key=lambda vsn: Rec.OptKey.unpack(vsn[2])))))
	  else:
	      return dict(spec._for_each(value, 
			  lambda c, vsn: ((n, transcode(v, s)) for (v, s, n) in vsn)))

      @__call__.intercept
      def alternative(self, value, spec:Sub(Alt)):
	  def alt(c, vsn):
	      error = None
	      for (v, s, _) in vsn:
		  try:
		      return transcode(v, s)
		  except TypeError as e:
		      error = e
	      raise error
	  print(spec, 'is alt!', value)
	  return spec._for_each(value, alt)

  transcode = Transcode()


As I said, you don't need to understand all that.  All you need to see is that
when you call the transcode() function, what is actually called can be any of
those methods above.  The method Transcode.sequence() handles lists of data,
while the method Transcode.map_instance() is the "core" that rewrites maps as
instance of particular classes.  And the method Transcode.__call__() is the
default method that's called if none of the other, specialised methods match
up with the specifications.

Andrew

Comment on this post