3 ms·
Just upgraded motioneye[1] Python 2 yesterday via pip, have been porting other smaller Python 2 projects to Python 3 for personal use for a while now. But ther
by Abishek_Muthian 6y ago
Just upgraded motioneye[1] Python 2 yesterday via pip, have been porting other smaller Python 2 projects to Python 3 for personal use for a while now.
But there are still large projects like motioneye where Python 3 port is WIP or not planned all.
[1]https://github.com/ccrisan/motioneye https://github.com/ccrisan/motioneye
- agucova 6y agoThere is a python3 branch, some issues around the topic and a PR [1] preparing for a transition. [1]: https://github.com/ccrisan/motioneye/pull/1978 https://github.com/ccrisan/motioneye/pull/1978
- Abishek_Muthian 6y agoYes there are, this[2] WIP PR is by the maintainer himself. It will be a while till the port is complete. [2] https://github.com/ccrisan/motioneye/pull/1572 https://github.com/ccrisan/motioneye/pull/1572
- rnestler 6y agoAccording to the contribution graph (https://github.com/ccrisan/motioneye/graphs/contributors https://github.com/ccrisan/motioneye/graphs/contributors) it was started in 2013 when Python 3.3 was already released. So what where the reaosons the project started in Python 2 in the first place?