#4037: Python script distribution standardisation -------------------------+--------------------- Reporter: Chris Johns | Owner: (none) Type: defect | Status: new Priority: normal | Milestone: 6.1 Component: admin | Version: 6 Severity: normal | Resolution: Keywords: | Blocked By: Blocking: | -------------------------+---------------------
Comment (by Chris Johns): Replying to [comment:17 Christian Mauderer]: > > > The last point is definitively a controversial one. There are good reasons for both directions. But again: Maybe that should be discussed with a broader audience? > > > > I think there will be some push back to dropping Python2 right now and this will fade as time goes on. > > There would be some advantages too. Maybe we should discuss an indicator that it is time to drop the python2 support (for example: as soon as waf does; or as soon as CentOS doesn't installs it by default; or in 1 year; or ...) so that there is a clear plan and it isn't discussed again and again every few months. But like you said: That's not the topic of this ticket and I think it would be better to discuss this on the mailing list. I think the new build system and the qual project need to be done and we have releases with them. I think at the core of this issue is releases with python 2 and 3 and once we know how they are traveling it will become apparent what we can do. I will remove the script support in the RSB and close this ticket when it is merged. -- Ticket URL: <http://devel.rtems.org/ticket/4037#comment:18> RTEMS Project <http://www.rtems.org/> RTEMS Project
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs