Skip to content

Instantly share code, notes, and snippets.

View djmunro's full-sized avatar

David Munro djmunro

View GitHub Profile
@djmunro
djmunro / data.py
Last active December 12, 2016 20:59
[-64, 0, 63.5, None]
[0, 50, 100, None]
[3, 15, 28.5, None]
[0, 1, 2, 3]
#I have 4 lists like what's seen above. I want a generator, when I call it will return the count of items at 1st, then 2nd,... index
#so from the above example, I want the following outpout
#>> next(), 4

Keybase proof

I hereby claim:

  • I am djmunro on github.
  • I am dmunro (https://keybase.io/dmunro) on keybase.
  • I have a public key ASAHTnjurd7-RPY113f8jK7m9PVKV5oiDb4LPocM35OsJgo

To claim this, I am signing this object:

import asyncio
import ctypes
import sys
import threading
from asyncio.base_futures import _PENDING
from functools import wraps
from typing import Callable, List, Generic, TypeVar
import aioprocessing
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Document</title>
<script
src="https://code.jquery.com/jquery-3.5.0.min.js"
integrity="sha256-xNzN2a4ltkB44Mc/Jz3pT4iU1cmeR0FkXs4pru/JxaQ="
crossorigin="anonymous"

Any top-level comment on pull request ought be tagged with one of four emojis:

  • for a non-blocking comment that asks for clarification. The pull request author must answer the question before the pull request is merged, but does not have to wait for the comment author to re-review before merging.

  • 🎨 for a non-blocking comment that proposes a refactor or cleanup. The pull request author does not have to address the comment for the pull request to merge.

  • ⚠️ for a blocking comment that must be addressed before the pull request can merge. The comment's author should leave a Request Changes review, and is responsible for re-reviewing once the pull request author has addressed the issue.

  • 😻 for a comment that compliments the author for their work.