Re: Dropping support for Python 2.7

2018-01-27 Thread Goodman, Alexander (398K)
Hi Michael, We actually discussed this in great detail today internally at JPL. I have not hosted the code anywhere yet, but am planning on putting it up on GitHub fairly soon once I have a more complete prototype and end-to-end example. When it's ready, I'll post a more formal announcement on the

Re: Dropping support for Python 2.7

2018-01-26 Thread Michael Anderson
Alex, Have you posted the pandas version anywhere yet? I'd be happy to lend a hand with the conversion if you have. Michael A. Anderson On Thu, Jan 18, 2018 at 10:17 AM, Goodman, Alexander (398K) < alexander.good...@jpl.nasa.gov> wrote: > Hi Michael, > > This isn't something we have made any h

Re: Dropping support for Python 2.7

2018-01-18 Thread Wilson, Brian D (398M)
Folks, The futurize and pasteurize components at http://python-future.org/ might be useful in developing a code base that runs on both python versions 2 and 3. By supporting both, you retain flexibility for scientific users. -- Brian On 1/16/18, 8:33 PM, "Goodman, Alexander (398K)" wr

Re: Dropping support for Python 2.7

2018-01-18 Thread Michael Anderson
“This has actually been the subject of (mostly unsuccessful) proposals. “ It would be interesting to know what some of those look like. Maybe one of the PMC could post a list of deprecate / maintain / incubate on the Confluence? While it might be something that can’t get funded internally, it

Re: Dropping support for Python 2.7

2018-01-18 Thread Goodman, Alexander (398K)
Hi Michael, This isn't something we have made any hard decisions about, but if you asked for my personal impression, I think just about everything outside the core ocw library is more or less in a deprecated state. The original developers of most of the code in these subfolders have stopped contri

Re: Dropping support for Python 2.7

2018-01-17 Thread Michael Anderson
On a related topic, what's the roadmap for the features outside of main ocw folder? Which of those will fold into the main ocw library, which will remain as they are and which will be deprecated? On Tue, Jan 16, 2018 at 11:33 PM, Goodman, Alexander (398K) < alexander.good...@jpl.nasa.gov> wrote:

Re: Dropping support for Python 2.7

2018-01-16 Thread Goodman, Alexander (398K)
Hi Lewis, I think that is sort of a hasty action to take. If anything, I question whether we should even require pydap as a dependency in the first place since its main advantage (when used as a client-side tool, anyway) is to provide the ability to load OpenDAP datasets without the netcdf4 librar

Dropping support for Python 2.7

2018-01-16 Thread lewis john mcgibbney
Hi Folks, You will notice that our TravisCI builds currently report as being broken. This is due to the pydap dependency not being available for Python 2.7. Is it time to drop support for Python 2.7 altogether and simplify things? Lewis -- http://home.apache.org/~lewismc/ http://people.apache.or