Podcasts about readthedocs

Sponsored by Sentry: Sign up at pythonbytes.fm/sentry And please, when signing up, click Got a promo code? Redeem and enter PYTHONBYTES Special guest: Anastasiia Tymoshchuk Brian #1: Using accessible colors, monolens & CMasher Tweet by Matthew Feickert, @HEPfeickert “I need to give some serious praise to fellow Scikit-HEP dev Hans Dembinski on his excellent monolens tool for interactive simulation of kinds of color blindness. It works really quite well and the fact that is a pipx install away is awesome! monolens lets you “view part of your screen in greyscale or simulated colorblindness” So simple. Just pops up a box that you can drag around your monitor and view stuff in greyscale. Reply tweet by Niko, @NikoSercevic “I mean to use cmasher so I know it’s cb friendly” CMasher : “Scientific colormaps for making accessible, informative and cmashing plots” Provides a collection of scientific colormaps and utility functions to be used by different Python packages and projects, mainly in combination with matplotlib. Lots of great colormaps that are color blindness friendly. Just specify the CB friendly colormaps with plots, super easy. # Import CMasher to register colormaps import cmasher as cmr # Import packages for plotting import matplotlib.pyplot as plt import numpy as np # Access rainforest colormap through CMasher or MPL cmap = cmr.rainforest # CMasher cmap = plt.get_cmap('cmr.rainforest') # MPL # Generate some data to plot x = np.random.rand(100) y = np.random.rand(100) z = x**2+y**2 # Make scatter plot of data with colormap plt.scatter(x, y, c=z, cmap=cmap, s=300) plt.show() Michael #2: rapidfuzz: Rapid fuzzy string matching in Python and C++ via Mikael Honkala Rapid fuzzy string matching in Python and C++ using the Levenshtein Distance “you mention fuzzywuzzy for fuzzy text matching in the last episode, and wanted to mention the rapidfuzz package as a high-performance alternative.” “non-rigorous performance testing of several alternatives (including fuzzywuzzy), and rapidfuzz came out on top with a sizable margin.” Simple Ratio example: > fuzz.ratio("this is a test", "this is a test!") 96.55171966552734 Anastasiia #3: Structlog to improve your logs One of the best ways to improve logs is to add more structure to them Why do we even need to care about logs? logs can provide visibility to production, what is actually happening logs can help to improve tracing of a bug, especially if logs are machine-readable and easy parseable logs can give you a clue why a bug or an exception occurred It’s super easy to start with Structlog, also easy to integrate it with ELK stack for further processing Features that you will get if switch your logs to use structlog: readable structure of logs in key-value pairs easy to parse with any post processor to visualise logs and to have more visibility for your code you can create custom log levels and separate specific logs with event keys for each log I am working with structured logs for a couple of years and recommend everyone to try Brian #4: xfail now works with pytest-subtests Admittedly, there may be few people that care about this, but I’m one of them. subtests are a kinda weird feature of unittest that came in with Python 3.4 They’re really a context manager that you can use within a test function pytest started supporting them through a plugin, pytest-subtests, sometime in 2019 With the plugin, you can use either the unittest style, or a fixture fixture style, without unittest. It’s a similar problem/solution that pytest-check solves to allow multiple failures per test case. But, like I said, they have some quirks. See Paul Ganssle’s Subtests in Python T&C 111: Subtests in Python with unittest and pytest One quirk is that xfail didn’t work right. It’s discussed in both links above. Anyway, it’s fixed now, thanks to maybe-sybr, as of version 0.5.0 So you can now trust that xfail will work properly with subtest Michael #5: BaseSettings in Pydantic via Denis Roy Create a model that inherits from BaseSettings The model initialiser will attempt to determine the values of any fields not passed as keyword arguments by reading from the environment. This makes it easy to: Create a clearly-defined, type-hinted application configuration class Automatically read modifications to the configuration from environment variables Manually override specific settings in the initialiser where desired (e.g. in unit tests) Get values from OS ENV or .env files Also has support for secrets files Anastasiia #6: Take care of the documentation on your team will thank you later Sphinx and ReadTheDocs will make life of developers so much easier Everyone knows importance of documentation, but how to keep it up to date? In my experience, I tried to use Confluence, describe new features in detailed Jira tickets, write some hints in Google docs and sharing them with the team. It does not work, as documentation is getting outdated and piles up drastically Benefits of implementing continuous documentation for the code: easy to support by writing docstrings, updating them when needed easy to find needed information in a centralised documentation easy to keep versioning for each new release of the code ReadTheDocs if free for open source code Sphinx will generate code reference documentation for the code Extras Michael pipx is now part of the PyPA (via Matthew Feickert) I’ll be “speaking” at Manning’s Developer Productivity conference. It’s free, so feel free to sign up. Cloud bills, they do pile up! Flake8-FastAPI (via Brian Skinn) Want to contribute to Jupyter? Add a localization. Brian pytest uses. Please comment on this thread if you know of some great projects that use pytest, if they converted from something else, or just find it interesting that they use pytest. Joke First time recursion

James and BIll talk about GDAL and OGR. James can't pronounce it correctly but he knows how to use it. Bill talks about how much it has been part of his workflows in the past 15 years. There is even more that didn't make the podcast via Howard Butler (https://twitter.com/howardbutler): GDAL Barn Raising Geodesy is a property of the data. When all our data came from paper maps, geodesy didn't matter as much except for the pocket protector crowd, but now that most of our positioning comes from space, geodesy buried in our data is an unavoidable topic. The open source stack of software based on GDAL and PROJ was deficient in the geodesy realm because PROJ was a cartographic transformation library (for making pretty maps!) rather than a geodetic library (for serious data management and engineering). Kristian Evers and Thomas Knudsen of Denmark SDFE (~ Denmark USGS) added the bits necessary to PROJ to allow it to act as a geodetic library as of the PROJ 5 release. The Barn Raising was needed to wire up those bits in PROJ 5 with the dictionaries that describe all of the transformations. This effort was three pieces – swapping out the GDALDATA and PROJLIB CSV files for a single, unified SQLite db, putting a OGC Well Known Text v2 engine in PROJ, wiring up GDAL, PROJ, libgeotiff, PostGIS, QGIS, and whoever else to use it all directly. The result of this effort is GDAL 3.0 and PROJ 6.1 Nyall Dawson has an excellent post describing how this effort improved QGIS https://lists.osgeo.org/pipermail/qgis-developer/2019-June/057525.html by making the software work better, more simple, and more unified with the rest of the other projects. gdalbarn.com has the history of the efforts of who pushed in money and Even's progress reports as he did the development. gdal.org refactor Even, myself, Mateusz, and Dan Baston at the OSGeo Community Sprint in Minneapolis refactored the gdal.org website to be based on Sphinx like geotools.org, mapserver.org, pdal.io, proj.org, and many other ReadTheDocs-based efforts. A primary goal was to allow you to hit the front page and be able grep for a driver name right away. The docs were buried, and this was an effort to bubble them up, and make it easier for people to contribute to them. For example, there's now a PDF https://gdal.org/gdal.pdf (900 pages!) and people can use Sphinx Intersphinx capability to link to GDAL documentation in their own projects. COG Driver Even just pushed an explicit Cloud Optimized GeoTIFF COG driver for GDAL that will be released in the next GDAL release that handles the writing side of COG. Your audience should know about COG.

Markdown e github. Un connubio fantastico.Scrivere velocemente il primo.Il secondo aiutare a migliorare contenuti con il contributo di tutti.Come ? ... buon ascolto !Ricordate: info@caffe20.it e area pro del caffe' per i materiali e le discussioni ( e anticipazioni !)

MRS 019: Eric Berry Today's episode of My Ruby Story is an interview with Eric Berry, who is our newest panelist on Ruby Rogues. [01:10] Introduction to Eric Eric is one of Chuck's friends from early in his programming career. Eric is @coderberry on Twitter. He's been a Ruby developer for about 9 years and doing software for about 19 years. [02:15] How Eric got into programming He was hired to do HTML for a company called vLender. Eric worked in Photoshop 2 (pre-layers). He, then, went on an LDS mission and while on his mission, he built a system to track the cars and assets for the mission. Then, his brother moved out to Switzerland to join an eCommerce company. Eric bought a PHP book, read it, got a passport, and started showing up at his work. Eventually they hired him. They started shifting over to Java. They coded Java with VIM. While in Switzerland, Eric and his brother had created an app that allowed them to share photos with family back home. His brother raised funds and they moved to England to build up the photo sharing app. They eventually sold shareaphoto.com to HP. Eric jokes that this was his "college." 9/11 hit and Eric's brother moved back to the states. Eric stayed for another 2 years, then moved to Las Vegas. He was a residential appraiser for about 4 years. While there, he built some software to help the company. Eric took a pay cut from $180,000 to $65,000 per year to go back to software. He and his wife eventually moved back to Utah and got a job working for AtTask (now Workfront) [10:43] Eric finds Ruby Eric and one of his co-workers went out and created projects with Django and Rails. They both loved Rails. Eric was using Rails at AtTask in the marketing department and spent a ton of time figuring out how to deploy Rails with mongrel. Eric has also worked for Omniture (acquired by Adobe), Instructure, and One-on-One Marketing. [14:12] Teach Me to Code screencasts and Chuck's story Initially, Eric created Teach Me to Code as an homage to Ryan Bates from RailsCasts. Eric left his mistakes and fumbling in. He got feedback from people that liked that it showed how to debug and figure out issues. Chuck came in to create content for Teach Me to Code. Eric's company and focus moved to Groovy on Grails which prompted him to hand the series off to Chuck. Eric mentions Chuck's tenacity. Teach Me to Code is a large part of Chuck's journey into podcasting. [19:11] Codesponsor Eric has been building other people's businesses for about 20 years. He's done all kinds of projects at all levels. He doesn't want to continue on a path where he doesn't participate in the end result of the project. Eric tried out AdWords. It'll pay off in 2-5 years, but he has not passion for it. Eric loves programming and developers and wanted to do something that served them. Open Source is starting to have problems with sustainability. People are building their businesses on top of software that's maintained by 1-2 developers. These folks have a day job and aren't paid to write their open source software. The get a bunch of requests for help and that workload doesn't go away. Then they get burned out. Then you have the "no longer maintained" notices on projects that you're using. Codesponsor solves this problem by bringing marketing into the picture to put some money into the developers' pockets and gives them some validation for what they did. Eric talks about a pay me button that Kent C. Dodds put on some of his repos. He didn't get any contributions. The problem with corporate sponsors is that the developer feels obligated to provide unpaid support when their sponsor has a problem. OpenCollective explained. Their biggest problem is money is not coming in. Open Design Collective CodeSponsor allows companies that want to get in front of developers to put non-obtrusive, subtle text ads in the README's and websites of the projects without creating the issues that come with direct sponsorship. Mention of ReadTheDocs.org [37:02] Eric's current work situation and Nate Hopkins Eric talks about Nate Hopkins and Chuck mentions that Nate Hopkins was his first mentor as a professional developer. Eric shares a funny story about Chuck and Nate working together. Picks Eric Carbonads.com Timber.io Rework podcast by Basecamp React Table Chuck Ruby Dev Summit React Podcast Plans - TBA Elixir Podcast Plans - TBA Dave Thomas' Elixir Course

MRS 019: Eric Berry Today's episode of My Ruby Story is an interview with Eric Berry, who is our newest panelist on Ruby Rogues. [01:10] Introduction to Eric Eric is one of Chuck's friends from early in his programming career. Eric is @coderberry on Twitter. He's been a Ruby developer for about 9 years and doing software for about 19 years. [02:15] How Eric got into programming He was hired to do HTML for a company called vLender. Eric worked in Photoshop 2 (pre-layers). He, then, went on an LDS mission and while on his mission, he built a system to track the cars and assets for the mission. Then, his brother moved out to Switzerland to join an eCommerce company. Eric bought a PHP book, read it, got a passport, and started showing up at his work. Eventually they hired him. They started shifting over to Java. They coded Java with VIM. While in Switzerland, Eric and his brother had created an app that allowed them to share photos with family back home. His brother raised funds and they moved to England to build up the photo sharing app. They eventually sold shareaphoto.com to HP. Eric jokes that this was his "college." 9/11 hit and Eric's brother moved back to the states. Eric stayed for another 2 years, then moved to Las Vegas. He was a residential appraiser for about 4 years. While there, he built some software to help the company. Eric took a pay cut from $180,000 to $65,000 per year to go back to software. He and his wife eventually moved back to Utah and got a job working for AtTask (now Workfront) [10:43] Eric finds Ruby Eric and one of his co-workers went out and created projects with Django and Rails. They both loved Rails. Eric was using Rails at AtTask in the marketing department and spent a ton of time figuring out how to deploy Rails with mongrel. Eric has also worked for Omniture (acquired by Adobe), Instructure, and One-on-One Marketing. [14:12] Teach Me to Code screencasts and Chuck's story Initially, Eric created Teach Me to Code as an homage to Ryan Bates from RailsCasts. Eric left his mistakes and fumbling in. He got feedback from people that liked that it showed how to debug and figure out issues. Chuck came in to create content for Teach Me to Code. Eric's company and focus moved to Groovy on Grails which prompted him to hand the series off to Chuck. Eric mentions Chuck's tenacity. Teach Me to Code is a large part of Chuck's journey into podcasting. [19:11] Codesponsor Eric has been building other people's businesses for about 20 years. He's done all kinds of projects at all levels. He doesn't want to continue on a path where he doesn't participate in the end result of the project. Eric tried out AdWords. It'll pay off in 2-5 years, but he has not passion for it. Eric loves programming and developers and wanted to do something that served them. Open Source is starting to have problems with sustainability. People are building their businesses on top of software that's maintained by 1-2 developers. These folks have a day job and aren't paid to write their open source software. The get a bunch of requests for help and that workload doesn't go away. Then they get burned out. Then you have the "no longer maintained" notices on projects that you're using. Codesponsor solves this problem by bringing marketing into the picture to put some money into the developers' pockets and gives them some validation for what they did. Eric talks about a pay me button that Kent C. Dodds put on some of his repos. He didn't get any contributions. The problem with corporate sponsors is that the developer feels obligated to provide unpaid support when their sponsor has a problem. OpenCollective explained. Their biggest problem is money is not coming in. Open Design Collective CodeSponsor allows companies that want to get in front of developers to put non-obtrusive, subtle text ads in the README's and websites of the projects without creating the issues that come with direct sponsorship. Mention of ReadTheDocs.org [37:02] Eric's current work situation and Nate Hopkins Eric talks about Nate Hopkins and Chuck mentions that Nate Hopkins was his first mentor as a professional developer. Eric shares a funny story about Chuck and Nate working together. Picks Eric Carbonads.com Timber.io Rework podcast by Basecamp React Table Chuck Ruby Dev Summit React Podcast Plans - TBA Elixir Podcast Plans - TBA Dave Thomas' Elixir Course

MRS 019: Eric Berry Today's episode of My Ruby Story is an interview with Eric Berry, who is our newest panelist on Ruby Rogues. [01:10] Introduction to Eric Eric is one of Chuck's friends from early in his programming career. Eric is @coderberry on Twitter. He's been a Ruby developer for about 9 years and doing software for about 19 years. [02:15] How Eric got into programming He was hired to do HTML for a company called vLender. Eric worked in Photoshop 2 (pre-layers). He, then, went on an LDS mission and while on his mission, he built a system to track the cars and assets for the mission. Then, his brother moved out to Switzerland to join an eCommerce company. Eric bought a PHP book, read it, got a passport, and started showing up at his work. Eventually they hired him. They started shifting over to Java. They coded Java with VIM. While in Switzerland, Eric and his brother had created an app that allowed them to share photos with family back home. His brother raised funds and they moved to England to build up the photo sharing app. They eventually sold shareaphoto.com to HP. Eric jokes that this was his "college." 9/11 hit and Eric's brother moved back to the states. Eric stayed for another 2 years, then moved to Las Vegas. He was a residential appraiser for about 4 years. While there, he built some software to help the company. Eric took a pay cut from $180,000 to $65,000 per year to go back to software. He and his wife eventually moved back to Utah and got a job working for AtTask (now Workfront) [10:43] Eric finds Ruby Eric and one of his co-workers went out and created projects with Django and Rails. They both loved Rails. Eric was using Rails at AtTask in the marketing department and spent a ton of time figuring out how to deploy Rails with mongrel. Eric has also worked for Omniture (acquired by Adobe), Instructure, and One-on-One Marketing. [14:12] Teach Me to Code screencasts and Chuck's story Initially, Eric created Teach Me to Code as an homage to Ryan Bates from RailsCasts. Eric left his mistakes and fumbling in. He got feedback from people that liked that it showed how to debug and figure out issues. Chuck came in to create content for Teach Me to Code. Eric's company and focus moved to Groovy on Grails which prompted him to hand the series off to Chuck. Eric mentions Chuck's tenacity. Teach Me to Code is a large part of Chuck's journey into podcasting. [19:11] Codesponsor Eric has been building other people's businesses for about 20 years. He's done all kinds of projects at all levels. He doesn't want to continue on a path where he doesn't participate in the end result of the project. Eric tried out AdWords. It'll pay off in 2-5 years, but he has not passion for it. Eric loves programming and developers and wanted to do something that served them. Open Source is starting to have problems with sustainability. People are building their businesses on top of software that's maintained by 1-2 developers. These folks have a day job and aren't paid to write their open source software. The get a bunch of requests for help and that workload doesn't go away. Then they get burned out. Then you have the "no longer maintained" notices on projects that you're using. Codesponsor solves this problem by bringing marketing into the picture to put some money into the developers' pockets and gives them some validation for what they did. Eric talks about a pay me button that Kent C. Dodds put on some of his repos. He didn't get any contributions. The problem with corporate sponsors is that the developer feels obligated to provide unpaid support when their sponsor has a problem. OpenCollective explained. Their biggest problem is money is not coming in. Open Design Collective CodeSponsor allows companies that want to get in front of developers to put non-obtrusive, subtle text ads in the README's and websites of the projects without creating the issues that come with direct sponsorship. Mention of ReadTheDocs.org [37:02] Eric's current work situation and Nate Hopkins Eric talks about Nate Hopkins and Chuck mentions that Nate Hopkins was his first mentor as a professional developer. Eric shares a funny story about Chuck and Nate working together. Picks Eric Carbonads.com Timber.io Rework podcast by Basecamp React Table Chuck Ruby Dev Summit React Podcast Plans - TBA Elixir Podcast Plans - TBA Dave Thomas' Elixir Course

Jake and Michael speak with Jason McCreary about Laravel Shift, LTS software, and getting git.

Stefan HASLINGER, Gregor PRIDUN, Anna GEIGER, Denis KNAUF und Horst JENS plaudern über freie Software und andere Nerd-Themen. Shownotes auf http://goo.gl/7K9M1H oder http://biertaucher.at