On Saturday, June 11, 2016 at 8:26:31 AM UTC-5, Marek Marczykowski-Górecki wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On Sat, Jun 11, 2016 at 06:17:54AM -0700, Jeremias E. wrote: > > Hello Marek, > > > > > > > > Is there any plan to port Qubes OS tools etc. to Pyhton 3 in the > future? > > > > > > Yes there is such plan for Qubes 4.x. > > > > > > How does the plan look like? What is your roadmap for achieving this? > > > > Do you consider to port or to rewrite qvm-tools? > > Most of python code will be/is rewritten in Qubes 4.0. It isn't > compatible with python 3 yet, but we're working on it. >
Is there anything the community could help with? Testing, porting or rewriting? What is about documentation for API's, tools etc.? When I was writing the Bug Report Tool I observed that many qvm-tools implement the same functionality something like is_vm_running or does_vm_exist etc. are functions which could be placed in a module and imported by each tool. In the case of the Bug Report Tool it would be possible to remove approx. 30% of the code by using such a module. What is your opinion on that? -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/24372338-df11-4083-91d4-95317e77b9fa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
