You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
start_time` in datetime - yes
just call it "start"
duration - this isn't great, but I store "hh:mm:ss" so that would be
easiest, but it's kinda lame. minutes is a handy int - makes it easy
to read the json and figure out if things are reasonable. 5, 20, 30,
120 makes way more sense than 300....
I would grab the code from the pycon/symposometing json feed - that
way the attribute names will all line up and I don't have to write new
code on my side. but it is kinda screwy, so feel free to make it
better, I'll adjust my code (like I get lists of stuff as strings, not
json lists.) Then maybe the prettier code can be pused up to sympzm.
On Fri, Apr 6, 2012 at 2:25 PM, Adam Cezar Jenkins [email protected]
wrote:
I'm assuming you want start_time in datetime. What do you want duration as? Seconds?
Reply to this email directly or view it on GitHub: #23 (comment)
json feed that provides the following:
For the next meeting meeting:
Group Name: "ChIPy"
Event Name: "April 2012 Meeting"
For each talk:
Presenter(s):
Contact email(s):
Title:
Start time:
Duration:
Description:
Released: yes/no.
Here is the app that consumes the data:
https://github.com/CarlFK/veyepar/blob/master/dj/scripts/addeps.py
The text was updated successfully, but these errors were encountered: