Caoimhinmg / PmagPy

Python-based tools for Paleomagnetic research
scripps.ucsd.edu
BSD 3-Clause "New" or "Revised" License
0 stars 1 forks source link

write up developer guidelines for switching from writing Python 2 to writing Python 3 #5

Open moonshoes87 opened 7 years ago

moonshoes87 commented 7 years ago

We want to make writing Python 3 an easy transition for current developers. I think a notebook could be a nice way to illustrate the changes from Python 2 to Python 3. There's a lot of nice examples here, although it might behoove us to be a little more concise for PmagPy people. Here's what seems important to me to include, in no particular order:

Additions? Subtractions?