Hi,
we all know that Python2 is end of life but several UDD code is using Python2. Is there any effort to port it to Python3.
we all know that Python2 is end of life but several UDD code is using Python2. Is there any effort to port it to Python3.
Not as far as I know. I suspect that, once it becomes necessary, it will
be easy to do given the codebase is relatively small.
Hi Lucas,
On Tue, Apr 14, 2020 at 08:47:11AM +0200, Andreas Tille wrote:
Not as far as I know. I suspect that, once it becomes necessary, it will be easy to do given the codebase is relatively small.
I agree that the small code base makes it probably easy. But I'm
worried about the "once it becomes necessary" part. We all know that Python2 is only alive due to our security team and we should actively
work on getting rid of the dependency rather sooner than later. Working "under pressure" makes things always uneasy - no matter how easy it
would be in principle.
I know probably nobody will stop me from doing it - but I'm hesitating adding another item on my table which is full of Debian Med - Covid-19 stuff. I'd volunteer to port those importers I've written myself once somebody gives the signal - but I'd love if those who have written the
core parts would take the lead (rather sooner than later).
I need to come back to this topic since I like to test the importers on
my local machines which are usually running testing.
Not as far as I know. I suspect that, once it becomes necessary, it will
be easy to do given the codebase is relatively small.
I agree that the small code base makes it probably easy. But I'm
worried about the "once it becomes necessary" part. We all know that
Python2 is only alive due to our security team and we should actively
work on getting rid of the dependency rather sooner than later. Working "under pressure" makes things always uneasy - no matter how easy it
would be in principle.
I know probably nobody will stop me from doing it - but I'm hesitating
adding another item on my table which is full of Debian Med - Covid-19
stuff. I'd volunteer to port those importers I've written myself once somebody gives the signal - but I'd love if those who have written the
core parts would take the lead (rather sooner than later).
On 13/05/20 at 16:38 +0200, Andreas Tille wrote:
Hi Lucas,
On Tue, Apr 14, 2020 at 08:47:11AM +0200, Andreas Tille wrote:
Not as far as I know. I suspect that, once it becomes necessary, it will
be easy to do given the codebase is relatively small.
I agree that the small code base makes it probably easy. But I'm
worried about the "once it becomes necessary" part. We all know that Python2 is only alive due to our security team and we should actively work on getting rid of the dependency rather sooner than later. Working "under pressure" makes things always uneasy - no matter how easy it
would be in principle.
I know probably nobody will stop me from doing it - but I'm hesitating adding another item on my table which is full of Debian Med - Covid-19 stuff. I'd volunteer to port those importers I've written myself once somebody gives the signal - but I'd love if those who have written the core parts would take the lead (rather sooner than later).
I need to come back to this topic since I like to test the importers on
my local machines which are usually running testing.
Use the Vagrant development environment?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 293 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 235:38:05 |
| Calls: | 6,624 |
| Files: | 12,172 |
| Messages: | 5,319,767 |