RT @baybryj: Python 3.6.2 release candidate 1 is now available for testing: go for it! #Python https://t.co/YSVCUh6Lmp
— Mariatta (@mariatta) June 18, 2017
Learn how to work with time in #postgres: https://t.co/wIud6Gsaas via @craigkerstiens
— Caktus Group (@CaktusGroup) June 15, 2017
RT @PythonEggs: How to convert JSON data into a #Python object https://t.co/XCWj5iiZTd
— Rob. PY (@py_coding) June 16, 2017
Simple Rest API Example and String Formatting (always learning) https://t.co/6yMdQ4KFSS by @gngrninja
— Python LibHunt (@PythonLibHunt) June 18, 2017
Microservices with Docker, Flask, and React (part 2) – from localhost to Amazon EC2 https://t.co/pxWl68vCsC
— /r/Python Popular (@RedditPython) June 12, 2017
Py is teaching people to code in “byte”-sized, gamified chunks. https://t.co/qH9ouu7weG
— Code.org (@codeorg) June 17, 2017
Instagram Makes a Smooth Move to Python3 https://t.co/a5BEEUA8DC “Performance speed is no longer the primary worry. Time to market speed is”
— Pybites (@pybites) June 16, 2017
RT @haxor: Check out this week’s @talkpython podcast where @mkennedy and I cover the best talks of #PyCon2017 https://t.co/KjE6CcZqqj
— Michael Kennedy (@mkennedy) June 13, 2017
Overlaying charts in Python – https://t.co/eHJFywo0ua https://t.co/G8iiTwGRWs
— Pycoders Weekly (@pycoders) June 17, 2017
RT @openNASA: Interested in joining #NASADatanauts? Engage with open data, learn skills, work on NASA projects or create your own! https://…
— RealPython.com (@RealPython) June 17, 2017
Tutorial for Faker, a library that generates placeholder data (names, addresses, …) for use in unit tests: https://t.co/UAlaLvEYUp
— Dan Bader (@dbader_org) June 17, 2017
HA!
RT @spolsky: I can tell this is not going to end well https://t.co/PMi3jYFFnf
— Vincent Driessen (@nvie) June 15, 2017
RT @AnalyticsVidhya: Cheat sheet with various codes and steps while performing exploratory #dataanalysis in #Python. https://t.co/ex6ca2kSR…
— Python Eggs (@PythonEggs) June 17, 2017
Birth Announcements for the Busy Father using #Python, Flask and @Twilio SMS https://t.co/zEB3BVZZey
— Full Stack Python (@fullstackpython) June 16, 2017
And something different. Take a look at the reply thread involving myself, Bob and @anthonyshaw that was started on the below Tweet. It’s a good example of how issues are identified and solved using code! Amazing job Bob! (The article is awesome too of course!).
How to write a great README for your GitHub project (tips + template you can use) https://t.co/hedbw7FWZn
— Dan Bader (@dbader_org) June 14, 2017