<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19170"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=532533608-03092014><FONT color=#0000ff
size=2 face=Arial>Hello,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=532533608-03092014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=532533608-03092014><FONT color=#0000ff
size=2 face=Arial>I think I have lost track. I am either with the people front
of Judea or the Judean people front. I don't think another meetup would do
anything other than split the group? I already think having a seperate womans
group is counter productive. If women feel uncomfortable or intimidated
then this should be discussed so we can change the culture to welcome
everyone.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=532533608-03092014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=532533608-03092014><FONT color=#0000ff
size=2 face=Arial>I do think there is a space for Educational/Presentational
effents that could have pizza and beer/coffee after. So yes if someone comes
along and wishes to organise its a good thing. BUT should not clash with
the timing of the pub meetup. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=532533608-03092014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=532533608-03092014><FONT color=#0000ff
size=2 face=Arial>Since I am emailing everyone Does anyone use Python in a GIS
context?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=532533608-03092014><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=532533608-03092014><FONT color=#0000ff
size=2 face=Arial>Cheers</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=532533608-03092014><FONT color=#0000ff
size=2 face=Arial>Glenn</FONT></SPAN></DIV><BR>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> Edinburgh
[mailto:edinburgh-bounces+glenn.bald=forestry.gsi.gov.uk@python.org] <B>On
Behalf Of </B>Mark Smith<BR><B>Sent:</B> 02 September 2014 16:59<BR><B>To:</B>
Python Edinburgh<BR><B>Subject:</B> Re: [Python Edinburgh]
Talks!<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr>Hi everybody,
<DIV><BR></DIV>
<DIV>In the past when I've asked around, there's been a general feeling that
we'd like to keep the pub meetups as they are and run talks separately. Before
Toms unilaterally changes the format of our main function can anybody who has an
opinion reply to this thread stating their preference.</DIV>
<DIV><BR></DIV>
<DIV>I think the options are:</DIV>
<DIV><BR></DIV>
<DIV>* Keep pub meetups as they are and run talks separately on a different
day.</DIV>
<DIV>* Start each meetup in a suitable venue (probably a local Python shop's
office) with a short talk, followed by a move to the pub</DIV>
<DIV>* Hold each meetup in suitable venue (see above) with a short talk and
(possibly free) beer and pizza.</DIV>
<DIV><BR></DIV>
<DIV>If anyone has any other suggestions, please also feel free to post
them.</DIV>
<DIV><BR></DIV>
<DIV>--Mark</DIV></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On 2 September 2014 11:12, Toms <SPAN dir=ltr><<A
href="mailto:toms.baugis@gmail.com"
target=_blank>toms.baugis@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=ltr>
<DIV>Hello again, this is the third and final email from me today :)</DIV>
<DIV><BR></DIV>
<DIV>I ran a quick survey last time and was extremely happy to see that as
well as there are people who have been coding in python for 5+ years, there
were also plenty who had just started or even are considering learning python
as their first programming language!</DIV>
<DIV>Apart from that, there was not a single person using the same stack -
there was so much diversity between 20 people, that there is enough fuel for
talks for a decade :)</DIV>
<DIV><BR></DIV>
<DIV>As such, I would like to tilt the format of the meetups by blending in
talks as the first part of the meetup. </DIV>
<DIV>Not just every now and then, but rather *each* time we meet. </DIV>
<DIV>Ideally we should be looking for 5-15 minute long talks, where no topic
is too big or too small. And they will be exciting as for the beginners, so
for the experts that might find a gap in their knowledge</DIV>
<DIV><BR></DIV>
<DIV>I'll give a few examples that i hope will spark your imagination as to
what kind of talk could you give:</DIV>
<DIV><BR></DIV>
<DIV>* lists, dicts, sets, tuples, namedtuples, frozensets - when to pick
tuple and when to pick list? </DIV>
<DIV>* decorators - how to write one and how and when to use one</DIV>
<DIV>* packing it up and shipping to PyPI with setuptools</DIV>
<DIV>* virtualenv, virtualenvwrapper, workon and other handy bits to make
managing python dependencies a breeze</DIV>
<DIV>* flask and writing a web app in 30 lines</DIV>
<DIV><BR></DIV>
<DIV>These are talks anyone experienced a bit in python could give - and there
are tons of others. I'm quite certain that it would spark discussions beyond
what any of us could imagine.</DIV>
<DIV><BR></DIV>
<DIV>During the last meetup I also asked a few of you as to what talk could
you give if they would be given these 5-15 minutes, here are some of
results:</DIV>
<DIV><BR></DIV>
<DIV>* Thomas wrote a quizz web app in python and has open sourced it and it
has picked up - so it's most certainly worth checking it out</DIV>
<DIV>* John - interprocess communication</DIV>
<DIV>* Alistair - conda</DIV>
<DIV>* The gentleman who's name is now escaping me (sorry!) - how the new
buzzy Go compares to python</DIV>
<DIV>* Manuel - "plone" - turns out that despite the rumors, plone is still
very much alive</DIV>
<DIV>* Ross - a full stack trace of a request - from browser down to where it
all began (some ruby might be involved)</DIV>
<DIV><BR></DIV>
<DIV>Here are few i can think myself from the top of the head, i could be
willing to present:</DIV>
<DIV>* docopt - the awesome self-documenting CLI lib</DIV>
<DIV>* adding autocomplete to your application in linux</DIV>
<DIV>* writing a desktop application in 100 lines on linux with GTK3</DIV>
<DIV>* automating deployment with fab</DIV>
<DIV>
<DIV>* forget httplib/urrlib and embrace requests</DIV></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>What's your stack like? </DIV>
<DIV>What's your favourite or most often used feature, library or framework
is? </DIV>
<DIV>What makes your head hurt and what excites you every time you get to use
it?</DIV>
<DIV><BR></DIV>
<DIV>Mail me privately with your talk ideas at <A
href="mailto:toms.baugis@gmail.com"
target=_blank>toms.baugis@gmail.com</A>!</DIV><SPAN class=HOEnZb><FONT
color=#888888>
<DIV><BR></DIV>
<DIV>Toms<BR></DIV></FONT></SPAN></DIV><BR>_______________________________________________<BR>Edinburgh
mailing list<BR><A
href="mailto:Edinburgh@python.org">Edinburgh@python.org</A><BR><A
href="https://mail.python.org/mailman/listinfo/edinburgh"
target=_blank>https://mail.python.org/mailman/listinfo/edinburgh</A><BR><BR></BLOCKQUOTE></DIV><BR></DIV><BR
clear=both>This email was scanned by the Government Secure Intranet anti-virus
service supplied by Vodafone in partnership with Symantec. (CCTM Certificate
Number 2009/09/0052.) In case of problems, please call your organisations IT
Helpdesk.<BR>Communications via the GSi may be automatically logged, monitored
and/or recorded for legal purposes.<BR><br clear="both">
+++++ The Forestry Commission's computer systems may be monitored and communications carried out on them recorded, to secure the effective operation of the system and for other lawful purposes. +++++<BR>
<BR>
The original of this email was scanned for viruses by the Government Secure Intranet (GSi) virus scanning service supplied exclusively by Cable & Wireless in partnership with MessageLabs.<BR>
<BR>
On leaving the GSi this email was certified virus-free<BR>
</BODY></HTML>