Closed quozl closed 4 years ago
Our em.py
was the same as upstream em.py
except for the shebang line, we had python2
(because some distributions use python3 as default 815303c), whereas upstream had python
No other changes were present in v3.3
and our current version
After the port, we should write python3
in shebang instead of python
since a lot of distributions still use python2
as default. If not, then we can remove our local em.py
files
As of https://github.com/sugarlabs/sugar-artwork/commit/29fc56cbbfc49af1f7c8c0930814ad174dc898f5, no other code changes are planned for sugar-artwork for the Port to Python 3 project, and sugar-artwork is ready to be tested using the native build environment method, making local packages, and release.
Thanks, looking forward to the release of artwork once tested. ;-)
Thanks. Release won't be for a while yet. We like to release sugar, sugar-toolkit-gtk3, sugar-datastore and sugar-artwork at the same time.
Agreed. Thanks!
Port to Python 3.
make local Fedora and Debian packages for testing by others.Python programs in
sugar-artwork
are used during build only.