The existing Python code in pycharm-project needs to be updated from Python 2 to Python 3 and perform similar to before. The following are technical considerations.
Do basic Python updates for version 2 -> 3 syntax and common packages.
Make sure that Python3 is being found, for example use python3 instead of python.
Review the code and respond to PyCharm PEP warnings.
Make sure that the step to upload files to cloud is configurable to use OWF AWS S3 storage bucket as well as State's GCP bucket, and for our testing only use AWS S3. Testing with local files is also OK.
Previously we developed and tested on Windows and deployed to GCP Ubuntu. Now we are developing and testing on Linux VB before deploying. It may be necessary to improve how the application is packaged and deployed locally so that it can be tested in deployed form. For example, this can be done with a simple bash script to tar up files, and then untar to install. Or we can try to use something like makeself. It may be worth using a Python virtual environment like GeoProcessor, but let's evaluate that once basic cleanup is done.
The existing Python code in
pycharm-project
needs to be updated from Python 2 to Python 3 and perform similar to before. The following are technical considerations.python3
instead ofpython
.makeself
. It may be worth using a Python virtual environment like GeoProcessor, but let's evaluate that once basic cleanup is done.