Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The reason function objects support arbitrary attributes is that, before we added that feature, several frameworks (e.g. parser generator ones) were abusing function docstrings (and other attribute of function objects) to stash away per-function information that was crucial to them -- the need for such association of arbitrary named attributes to function objects being proven by example, supporting them directly in the language rather than punting and letting (e.g.) docstrings be abused, was pretty obvious.</p> <p>To support arbitrary instance attributes a type must supply every one of its instances with a <code>__dict__</code> -- that's no big deal for functions (which are never tiny objects anyway), but it might well be for other objects <em>intended</em> to be tiny. By making the <code>object</code> type as light as we could, and also supplying <code>__slots__</code> to allow avoiding per-instance <code>__dict__</code> in subtypes of <code>object</code>, we supported small, specialized "value" types to the best of our ability.</p>
    singulars
    1. This table or related slice is empty.
    1. POPython Language Question: attributes of object() vs Function
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAlex Martelli
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPython Language Question: attributes of object() vs Function
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks Alex, for this inside view of *object*. I hope the gain in space was worth the effort. I still find it counter-intuitive that (a) the base class of the object system does not support one of the basic features of OO - instance attributes; and (b) this feature all of a sudden springs into existence with any non-sensical derived class *class Foo(object): pass*, which I find myself using more than often just to get instance attributes.
      singulars
      1. PO
      1. USThomasH
    2. CO@Thomas, are you equally surprised that Object in Java "does not support one of the basic features of OO" in exactly the same way? Its direct instances don't have instance attributes either. C# is the same, I believe. Since (and this is REALLY a basic feature of OO's: Liskov's Principle!) no subclass can take away something that's in the superclass, to satisfy your intuition would actually cost infinite memory: a dict should then have a __dict___... and THAT dict should of course have its OWN __dict__... and it can NEVER, NEVER stop. Your intuition's misleading you *A LOT*!-)
      singulars
      1. PO
      1. USAlex Martelli
    3. CO@Alex Ok, I hear you. But maybe this would all be possible if the \_\_dict\_\_'s of lean objects were lazy?! I actually could envision myself wanting to annotate the \_\_dict\_\_ of a \_\_dict\_\_ of an *object* instance with a little attribute, and it would be perfectly enough for me if this \_\_dict\_\_ would only spring into existence when I first assign to it. How is that?
      singulars
      1. PO
      1. USThomasH
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload