Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Either reference the functions on the module object:</p> <pre><code>import gm def stats(list): stats = {} # empty dict named stats stats['average'] = gm.avg_list(list) # Stats(key)[average] = mean of the list of numbers [values] stats['median'] = gm.median(list) # same for median return stats </code></pre> <p>or import the functions directly into the global namespace:</p> <pre><code>from gm import avg_list, median def stats(list): stats = {} # empty dict named stats stats['average'] = avg_list(list) # Stats(key)[average] = mean of the list of numbers [values] stats['median'] = median(list) # same for median return stats </code></pre> <p>Note that <strong>you should not name a variable <code>list</code></strong>. This masks the built-in <code>list()</code> function / type and can cause confusing errors later if you need to use it.</p> <p>You can write</p> <pre><code>stats = {} # empty dict named stats stats['average'] = avg_list(list) # Stats(key)[average] = mean of the list of numbers [values] stats['median'] = median(list) # same for median return stats </code></pre> <p>as</p> <pre><code>stats = {'average': avg_list(list), 'median': median(list)} return stats # or just return the dict literal, no real need to give it a name. </code></pre> <p>I think you should look at the first branch of your <code>median</code> function. Does the list need to be sorted there too, like in the second branch?</p> <p>Your <code>avg_list</code> function is also masking a built-in function, <code>sum()</code>, which you could use here instead of manually adding:</p> <pre><code>def avg_list(list): avg = float(sum(list))/len(list) print avg </code></pre> <p>Finally, look at the last line of that function -- it's <code>print</code>ing the <code>avg</code>, but <code>stats</code> is expecting it to <code>return</code> the <code>avg</code>. The two aren't the same.</p>
    singulars
    1. This table or related slice is empty.
    1. POImport troubles
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USagf
    1. USagf
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POImport troubles
      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. VTAcceptedByOriginator
    1. COIf I add sorted to the first branch, I receive a TypeError: 'int' object is not iterable.
      singulars
      1. PO
      1. USG.G
    2. CO@G.G You can't just wrap the whole thing in `sorted`, I mean you need to sort the list _before_ looking up the median, whether the list has an odd or even number of entries. Try just adding `list = sorted(list)` or `list.sort()` to the top of the function and get rid of the other calls to `sorted`.
      singulars
      1. PO
      1. USagf
    3. CO@afg ah, my mistake... I can do that. I ran the program again with the proper imports and came back with a: >>> stats([2,5,6,7,8]) 5.6 {'average': None, 'median': 6}
      singulars
      1. PO
      1. USG.G
 

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