Re: Code to Joy in The Economist (June/July 2018)
kirby urner <[email protected]>
| Newsgroups | gmane.comp.python.education |
|---|---|
| Message-ID | <CAPJgG3T9-HKBdZFxJNmbS1_VoM9qYAXn5W_L=D1wuxSE+Awo-Q@mail.gmail.com> |
On Sat, Jun 2, 2018 at 1:13 PM, kirby urner <[email protected]> wrote: > > > > Name : Object :: Luggage Tags :: Suitcase > Fixing this: Names: Object :: Luggage Tags : Suitcase (a ratio of ratios, would show this way it next books in my era, as in "this is to that :: ("as") that is to this other" and so on). I appreciate the Pycon 2018 account / perspective Naomi. Glad to know Andrew was attending in person and is reaping the benefits of joining a subculture / community, not just learning a computer language [ these go together, as most but not all, science fiction writers failed to predict i.e. that computer languages create tribalism in a positive way ]. Tangential remarks: * I just discovered Pyx this morning: http://pyx.sourceforge.net/ * I've made progress using RhinoScript (rs) a Python module compatible with 2.7 that runs inside a CAD system (proprietary, not unlike ESRI Arc* in that regard). * compiling PostGIS version of postgesql on old OSX Yosemite fails in the homebrew recipe, after about 5 hours doing OK. More in blogs happy to yak off-list. Kirby Kirby Kirby > > One suitcase (object) may have many names (connects to garbage collection > discussion). However at any one moment, a name points to only one object > (the same name in different modules, both running, still count as different > names -- scope matters). > > So yeah, the object itself is a "container" but what it contains may be > tags to other objects. > > Without this separation of "names" from "objects" there's an inevitable > tendency to imagine copies, as how can we have two bowls or boxes with > exactly the same content. > > We don't have a visual metaphor for "two suitcases containing exactly the > same clothes at the same time". > > But we do understand "one suitcase having two or more luggage tags." > > Surely we have two copies, albeit clones of the same thing. Not so in > Python though. Python is biased against making gratuitous copies of > anything. Keep is spare! (sparse if possible). Don't clutter memory with > excessive redundancy. > > > Kirby > > ** > http://4dsolutions.net/presentations/pycon2013.pdf > > > _______________________________________________ Edu-sig mailing list [email protected] https://mail.python.org/mailman/listinfo/edu-sig