Skip to content
This repository has been archived by the owner on Oct 6, 2024. It is now read-only.

Move to python 3 #23

Open
JotaRandom opened this issue Jun 2, 2017 · 1 comment
Open

Move to python 3 #23

JotaRandom opened this issue Jun 2, 2017 · 1 comment

Comments

@JotaRandom
Copy link

Move the project to python 3 could allow us to implement it in ponysay (or ponysay-tool u other tool) seamless and without adding more deps.

also it could be a good oportunity to revive the project and ponysay code; also review the name or the bundled tool.

Also it could be helpfull to avoid problems [1] if something ended affecting openjdk in that second trial apeal in times like this.

[1] https://en.wikipedia.org/wiki/Oracle_America,_Inc._v._Google,_Inc.

@maandree
Copy link
Owner

maandree commented Jun 2, 2017

I agree.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants