114 captures

01 Sep 2015 - 28 Nov 2025

Oct	NOV	Dec
	11
2019	2020	2021

success

fail

About this capture

COLLECTED BY

Organization: Archive Team

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.

The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.

This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.

Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.

The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.

Collection: Archive Team: URLs

TIMESTAMPS

The Wayback Machine - http://web.archive.org/web/20201111234216/https://www.fullstackpython.com/python-2-or-3.html

Full Stack Python All topics | Blog | Supporter's Edition | @fullstackpython | Facebook | What's new?

Python 2 or 3?

The Python programming language is almost finished with a long-term transition from version 2 to version 3. New programmers often have questions about which version they should learn. It can be confusing to hear that Python 3, which was originally released in 2008, is still not the default installation on some operating systems such as macOS. However, that situation is rapidly changing as the final version 2 release, Python 2.7, is approaching its end-of-life that is definitively scheduled for January 1, 2020. The simple answer right now is: learn Python 3, specifically the latest version which as of October 2019 is Python 3.7. If for some reason you absolutely have to learn Python 2, for example because your employer is working on a bunch of legacy code, you will be able to transfer the majority of your knowledge from Python 2 right into Python 3. Likewise, you will still be able to read and write Python 2 code if you start with Python 3. There are enough great resources out there that will teach you to code in version 3 without any prior version 2 experience. Python 3 is the future and you will not regret starting with the latest version of the programming language. There is one small caveat to the recommendation to go full-on Python 3. You may infrequently come across lesser-used open source code libraries that were originally written in Python 2 that do not completely support Python 3. That was the case before 2019 with DevOps configuration management tools such as FabricorAnsible. However, those libraries now support Python 3 and the usage problems that were frequent in years past are now typically not a concern. Knowing how to upgrade Python 2 libraries to 3.x is still a useful skill to apply at the edges of the Python open source community.

Visualizations and Projects

Since upgrading from Python 2 to 3 has been such a huge undertaking within the community, many projects have sprung up to make the transition easier. six is a 2/3 compatibility library that is a dependency for many popular Python projects to make it easier to support both Python 2 and 3 at the same time. Python 3 Readiness is a visualization of which most popular 360 libraries (by downloads) are ready to be used with Python 3. The Python clock counts down the time until Python 2.x is no longer maintained. While Python 2's retirement may still seem a long time away, it can take a lot of time and effort to migrate existing application to the modified syntax in 3.x.

Porting to Python 3 resources

Moving an existing codebase to Python 3 from 2 can be a daunting task, These resources were created by fellow developers who've previously gone through the process and have advice for making it less painful. Python 3 Porting is an entire book with details for how to upgrade your existing projects and libraries to Python 3.x. Moving from Python 2 to Python 3 is a PDF cheatsheet for porting your Python code. The official porting code to Python 3 page links to resources on porting Python code as well as underlying C implementations. There is also a quick reference for writting code with Python 2 and 3 compatibility. Upgrading to Python 3 with Zero Downtime supplies advice on transitioning a large existing Python 2 web application to Python 3. Their process involved upgrading dependencies, testing and deploying the new version before going back to clean up unnecessary code created by the transition. Migrating to Python 3 with pleasure is a porting guide that focuses on code that data scientists would typically use in their programs. Instagram Makes a Smooth Move to Python 3 explains their upgrade process for getting all of their code over to Python 3 compatibility over a period of about a year. Practical steps for moving to Python 3 is a podcast episode that goes over migrating a large existing application's codebase to Python 3 from Python 2. Lessons learned from migrating to Python 3 covers how a development team with a large e-commerce site built on Django was able to upgrade their project.

Python 2 to 3 resources

The following resources will give you more context on how the community feels the transition from Python 2 to 3 is going, as well as why you should upgrade as soon as possible. Why should I use Python 3? is a detailed FAQ on important topics such as unicode support, iteration improvements and async upgrades provided by 3.x. There is also a great follow up post by the author titled A Rebuttal For Python 3 that counters some arguments made by other community members who are unhappy about various features in Python 3. Want to know all of the advantages and what's changed in Python 3 compared to Python 2? There's an official guide to Python 3 changes you'll want to read. Python 3 is winning presents data and graphs from PyPI to show that at the current rate, by mid-2016 overall Python 3 library support will overtake Python 2 support. Python 3 Retrospective from the Benevolent Dictator for Life is a talk by Guido van Rossum on what is working, not working and still needs to be done before the changover can be considered complete. The stages of the Python 3 transition provides perspective from a core Python developer on how the transition from Python 2 to 3 is going as of the end of 2015. How Dropbox rolled out one of the largest Python 3 migrations ever explains how their transition began in 2015 and was successfully completed in 2018. There is also a follow up post on incrementally migrating over one million lines of code from Python 2 to Python 3 that has more details on how hack weeks were able to help make enough progress so the engineers could better estimate the scope of work when the transition from 2 to 3 became critical to their development toolchain. Zato: A successful Python 3 migration story examines the background, preparation, execution and testing of moving an existing Python 2 code base over to Python 3. Why Python 3? randomly outputs valid reasons to use Python 3 over 2.x. Rules for Radicals: Changing the Culture of Python at Facebook is a fascinating look at how Facebook moved from primarily Python 2 up to Python 3 due to the efforts of a small passionate group of developers within the company. Definitely worth watching to understand how to shift a large organization with an established codebase. Porting to Python 3 is like eating your vegetables explains that there are treats in Python 3 that are worth porting for and has some tips on making the transition easier. Scrapy on the road to Python 3 support explains from the perspective of a widely used Python project what their plan is for supporting Python 3 and why it has taken so long to make it happen. All major scientific Python libraries have pledged to drop Python 2 support no later than 2020, when Python 2's maintenance life is over. The pledge strongly encourages Python 3 adoption by publicly stating their intentions. 10 awesome features of Python that you can't use because you refuse to upgrade to Python 3 is a great slideshow with code snippets that show useful new features of Python 3 that are not available in 2.x such as keyword-only arguments, chained exceptions and the yield from keyword.

What's next now that you know about Python versions?

What editor should I use to code my Python app? I want to learn how to code a Python web application using a framework. Show me a list of the best Python learning resources.

Sponsored By

Software errors are inevitable. Chaos is not. Try Sentry for free.

The most accurate speech-to-text API. Built for Python developers.

Table of Contents

1. Introduction Learning Programming Core Language Why Use Python? Python 2 or 3? Enterprise Python Python Community Companies using Python Best Python Resources Best Python Videos Best Python Podcasts 2. Development Environments 3. Data 4. Web Development 5. Deployment 6. DevOps Changelog What Full Stack Means About the Author Future Directions Page Statuses ...or view the full table of contents.

Full Stack Python

Full Stack Python is an open book that explains concepts in plain language and provides helpful resources for those topics.

Updates via Twitter & Facebook.

Chapters

1. Introduction » Python 2 or 3? 2. Development Environments 3. Data 4. Web Development 5. Deployment 6. DevOps Changelog What Full Stack Means About the Author Future Directions Page Statuses ...or view the full table of contents.

Matt Makai 2012-2020