addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1light-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

OCPython Main Mtg: 2013.12(packaging, Unittest, licensing, &more via cmts!)+

  • Dec 23, 2013 · 5:30 PM
  • This location is shown only to members

MEEvtL MITE5M: RSVP & post thoughts now.

MEQNTI:  Orange County  Python-related  (OCPython)
people, news&Qs, some presentations, training/discussions/projects&hacking

{MKA4JN=And doing all that, & in that order, we do Recurring Agenda & Activities M0TAGN, since our[masked] meeting.}
{MX6417=As always, BRING YOUR LAPTOPS.} 
{MXODW9=Event listing RSVP Qs: MXNIIMs}
{MY58FR=Everyone, PLEASE POST OFTEN & PROPERLY, especially what you desire & why, and instead-of Private Messaging (as calls,emails, &even SMS); especially please:
* ASAP Post Topics, Presentations, Events, Qs, Jobs, & Announcements you want, and 
* ASAP RSVP (& if MAYBE, say YES till certain NO),
* one thread per topic & one topic per thread --read each link here for details.} 

{MFOITP: Recent+Upcoming Occurrences plus Changes in Effect Today, in order of start time:

MK96K2:[masked]- member Dan Stromberg founds group

MK979B: Repeat: every 1 month

MK984Z: [masked]Thu18:30: 1st occurrence

MK8VHB: [masked]~-present: member DestinyArchitect is Co-Organizer (so now 2 group leaders)

MK97XF: Food&drinks available to those who RSVP YES via cost-recovery.
M0TBVL: typically Quality 3-topping Round-Table Pizza, "the nutrition of hackers world wide", plus soda!

MTNQUI: [masked]Mon[masked]
Post potential topics in comments.
MTNQV0: [masked]Mon[masked] aka  mistake(to be rescheduled as Thanksgiving); on as planned; features start of Chromecasting, IP & software licensing, & more.
{MWU2DD=[masked]Mon[masked] aka topics include Python packaging & unit testing including Unittest , licensing (including a novel solution) by Destiny, and post more topics comments =MWU2DD}
{MY57PP=[masked]Mon[masked] aka post topics in comments=MY57PP}

MHQ8ST: Want more folks attending, plus great events totally suiting you? Then MAKE IT HAPPEN! -click here! including:
MIUMNL: Especially if a long drive for you, post a comment ASAP saying you're open to carpooling and we'll try to find you one.
MGDVWD: Bring your devices for accessing Meetup and working on programming: your smartphone & especially laptop.
MIUMRZ: During the event, or sooner, RSVP to our upcoming events whereever you can say MAYBE or YES.

LG4OWH: What are these codes as “LG4OWH:” on this point? They’re short IDs to date-stamp, uniquely-reference, & portably-track most any point or item.

MITDX1: Listing History, in order

MIFGYY: all entries & changes by I Destiny unless noted here.
{MWU1H2=This listing Meetup auto-created by copying the prior listing [masked]) (then I edited to fit); so for prior history & versions, see that the prior listing=MWU1H2}
{MY57KQ=title: updated from(OC-Python Main Meetup:[masked](Chromecasts, training&hacking, &more via cmts!)+) to present; added next occurrence MY57PP; removed prior history; from upcoming  copied MX6417,MXNS8C, MXNS38,  MXODW9 then edited to present, including replaced MXNS8C with MY58FR; updated quote(MEQNTI: Python-related discussion & presentations & hacking) and then quote(MITE5M: RSVP & comment now.)to present content; moved indeed factored MEQNR7 to MKA7N5 to htttp:// ; updated & moved quote(MKA4JN: Agenda & General Activities:) and used to replace MXNS38; pst[masked]Fri2337; cut quote(MKAA5N: but I'm shooting for future meetings going to 4hr (as 6:00pm-10:00pm) to do this agenda comfortably & fully.) as just detracts here; small updates; pst[masked]Fri2349=MY57KQ} 
{MY62D7=MKA4JN: update; {MY6302=MEQNTI: prepend "some " to "presentations" so put more interest on the other items as those easier to do & more participatory; suffix subject (here "Python") with "-related" to avoid application to just the subsequent group name}; update title fr(OC-Python Main Meetup:[masked](Chromecasts, training&hacking, &more via cmts!)+) to present; pst[masked]Sat0929=MY62D7}
{MY79WQ=title topics: suffixed q(licensing, ) and spaced;MWU2DD: add q(licensing (including a novel solution) by Destiny,); pst[masked]Sun0054=MY79WQ}

Join or login to comment.

  • Kenneth M.

    For all of those who attended and wanted my contact information, my email is [masked]
    My linkedin is at the following address:

    December 24, 2013

  • A former member
    A former member

    Do we have any topics scheduled? Is there anything someone wants to present or wants presented?

    Would anyone be interested in a Python packaging howto, or an introduction to unit testing with unittest howto?

    December 20, 2013

    • Dan S.

      I'd find packaging interesting.

      December 20, 2013

  • A former member
    A former member

    Intro to unittest would be great. :-)

    December 20, 2013

15 went

  • Dan S.
    of Laguna Niguel; 2010.01.27-,46+RSVPs,35+attends, Organizer,
    Event Host
  • Kenneth M. +1
    of Tustin; 2013.12.15-;1+RSVP,1+attends; web coder
  • absentia
    of Mission V;2013.12.23-;0+RSVP,1+attends;Nexus(IT VAR)sales&eng
  • A former member
  • A former member
  • A former member
  • A former member
  • A former member
  • A former member
  • A former member

Your organizer's refund policy for OCPython Main Mtg: 2013.12(packaging, Unittest, licensing, &more via cmts!)+

Additional notes: MK8SI7: free now, but prepare for soon a nominal attendance fee as very successfully done see 2012.08.27 by OCAndroid , latest example in .

Payments you make go to the organizer, not to Meetup. You must make refund requests to the organizer.

Regardless of the refund policy set by the organizer, Meetup may issue refunds on an organizer's behalf if we determine that Meetup's Payment Policies have been violated.

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy