Differences between revisions 64 and 66 (spanning 2 versions)
Revision 64 as of 2019-08-30 16:14:01
Size: 12078
Revision 66 as of 2020-01-20 14:38:21
Size: 12093
Deletions are marked like this. Additions are marked like this.
Line 33: Line 33:
 * link HTML (<a href="http://url/">name of the event</a>):  * HTML link using the format <a href="http://url/">name of the event</a>:
Line 119: Line 119:
 * Oier Etxaniz

(Yes, we could need some more help :-) )

The following people are inactive team members with admin rights to the calendars:

 * Anton Caceres
Line 120: Line 127:
 * Oier Etxaniz
 * Anton Caceres

(Yes, we could need some more help :-) )

The following people are inactive team members with admin rights to the calendars:

Python Events Calendar

The Python events calendar is a combination of Google calendars maintained by the Python Calendar Team and published on the following sites:

The events are also listed on a map mashup created by Luis Miguel Morillas:

Here's a snapshot showing all events from Jan 2012 - March 2016:


Submitting an Event

If you would like to get new events listed on these calendars, please write to events@python.org using the following email template:

Please add the following event:

 * name of the event: 
 * type of event: 
 * focus on Python: 
 * approximate number of attendees: 
 * location (incl. country): 
 * dates/times/recurrence (incl. time zone): 
 * HTML link using the format <a href="http://url/">name of the event</a>: 

Please mention:

  • the name of the event (including the user group name for user group events)
  • type of event (conference, bar camp, sprint, user group meeting, etc.)
  • focus on Python and approximate size (number of attendees)
  • the location (venue address, including city and country)

  • the dates/times (including the time zone)
  • a link with more details for the event (using HTML format "<a href="http://url/">name of the event</a>")

For recurring events, please also include the recurrence information, e.g. "monthly, every second Thursday".


  • For online events, please use "Online Event" as location.
  • For trainings, courses, webinars and similar type of events, please post your event on the PythonTraining page. We currently do not have a calendar for these.

  • /!\ Please leave at least 4 weeks notice when submitting events. The calendar team is volunteer driven. While we try to add new events swiftly, we cannot guarantee response times.

Bulk Submission of Events

In some cases, the email format may not be suitable, e.g. if you want to submit several larger events in one go. For those cases, please list the events in the email sent to events@python.org, including the following details:

  • the name of the event (including the user group name for user group events)
  • type of event (conference, bar camp, sprint, user group meeting, etc.)
  • focus on Python and approximate size (number of attendees)
  • optional: a link with more details for the event

for each event, or as summary, so that we can tell which type of event you want entered and whether they are suitable for our calendars.

Please attach the event data as iCal file events.ics using the following entry format:

  • title: name of the event

  • start and end dates: start day and end day of the event, entered as "all day events" for larger events, or as start and end date and time in the local timezone for smaller single day events

  • location: city, [state,] country

  • description: <a href="http://url/">name of the event</a>

The same notes as above apply to bulk submissions.

Available Calendars

iCal Downloads

RSS Feeds

Note: Google has switched off calendar RSS feeds on Nov 18 2015, so these links no longer work.

Twitter Feed

  • @PythonEvents

    This Twitter account automatically gets all new entries from both calendars as tweets. The triggering is setup using IFTTT. Note that changes to the calendar entries are not reported on the Twitter feed. This appears to be a limitation of the IFTTT trigger.

Embedding Calendars

If you'd like to embed the calendar into your site, please ping us at events@python.org before doing so. We'd like to keep a list of sites where the calendars are displayed.

You can find the embedding code further below on this page.

Known sites embedding the calendars

Python Calendar Team

The following people are active team members with have admin rights to the calendars:

  • Marc-Andre Lemburg
  • Oier Etxaniz

(Yes, we could need some more help :-) )

The following people are inactive team members with admin rights to the calendars:

  • Anton Caceres
  • Sergey Sokolov
  • Marcelo Elizeche Landó
  • Richard Jones
  • Mike Müller
  • Tarek Ziade
  • Tetsuya Morimoto
  • Skip Montanaro
  • Tim Golden
  • Mats Wichmann
  • Laura Creighton
  • Carol Willing

Mailing List

The team uses the python-events mailing list for discussion and to process events. The events@python.org address is an alias for the python-events mailing list.

Guidelines for entries

In order to make the decision of whether to add an event and where to add it easier, we've setup a few guidelines:

General Requirements

  • Events have to have some focus on Python: The event should either target Python, a project written in Python, or showcase Python in some form.

    Examples are Python conferences, conferences which have a Python track or tutorial, conferences at which Python is presented in some form. The same goes for conferences which target a project written mostly in Python (e.g. Plone, Django, OpenStack, etc.) and for other events such as sprints.

  • The calendars should only list the events themselves. CFP deadlines, registration openings or similar announcements should not be listed in the calendars.
  • For online events, such as PyWeek game jams, only a reasonably short events (no longer than two weeks) should be added as single event. For longer events, it's better to just add the start and end date as separate events to the calendar. The same criteria for calendars apply to online events as well. Please add these using Online Event as location.

Calendar Choice

  • Python Events Calendar: This calendar should only receive entries for conferences of at least around 100 attendees, which at least around a 3rd non-local attendees. Smaller events with at least around 30 attendees such as sprints, barcamps, PyDays or smaller unconferences may also be added to this calendar if they are scheduled as separate event, will have a significant impact and reach out to larger regions. Examples: PyCon conferences, OSCON, Django conferences, Plone conference, Need-for-speed sprints, Python BarCamps/Unconferences/etc.

  • Python User Group Calendar: This calendar is meant for user group activities which are open to Python people from outside the group (new prospective members and visitors from out of town). It is not meant for user group internal events. Examples: monthly local user group meetings, project sprints that are open for non-group members, workshops organized by user groups, Django Girls events.

Notes regarding calendar entries

Some notes regarding entries for the admins:

  • Please add the conference/event year to the title, if available. For user group meetings or other events that occur more often that's probably not necessary.
  • For conferences please use "All day" events, for user group events please add the start time and end time, if known. Full day user group events can also be added as "All day" event to give them a little more attention in the calendar.
  • Please include the location as "City, Country".
  • Please add a link to the event as description. We found that using HTML links works well, e.g. <a href="http://www.pycon.fr/2012/>PyCon FR 2012</a>

  • Please don't add more than the link to the description. If an event does not have a website, it's fine to add a one line text description. Background: The entries should not be used as advertisement text for events, only as reference.
  • Please don't select an event color. People who subscribe to the calendars will have their own color preferences, so it's better to leave the default color set for all events.
  • Reminders should not be setup for the events. They can be annoying for users subscribing to the calendars.
  • We've always used "Show me as: Available" for new entries. No idea whether that matters or not.
  • Please select "Privacy: Default" for new entries. This makes the entries public, since that's the default setting.

All calendar admins can invite more people as calendar admins. When doing so, please add the new admins to the above list and ping the team by writing to events@python.org (also to get their email address added to the python-events mailing list).

Calendar embedding code

This iframe code is used on pycon.org to display the calendar:

  • <iframe src="https://www.google.com/calendar/embed?showTitle=0&amp;showCalendars=0&amp;height=400&amp;wkst=2&amp;bgcolor=%23FFFFFF&amp;src=j7gov1cmnqr9tvg14k621j7t5c%40group.calendar.google.com&amp;color=%23125A12&amp;src=3haig2m9msslkpf2tn1h56nn9g%40group.calendar.google.com&amp;color=%232F6309&amp;ctz=Europe%2FLondon" style=" border-width:0 " width="800" height="450" frameborder="0" scrolling="no">
      <a href="https://www.google.com/calendar/ical/j7gov1cmnqr9tvg14k621j7t5c%40group.calendar.google.com/public/basic.ics">Python Events iCal Calendar</a><br/>
      <a href="https://www.google.com/calendar/ical/3haig2m9msslkpf2tn1h56nn9g%40group.calendar.google.com/public/basic.ics">Python User Group iCal Calendar</a>


PythonEventsCalendar (last edited 2020-02-27 09:18:53 by MarcAndreLemburg)

Unable to edit the page? See the FrontPage for instructions.