exclude obsolete packages and include alternatives

[shelper]

i wonder if 360 list includes some packages that have not been updated for a long time.
these packages can be out-of-date and replaced by new packages.
it might just because their long existance in the past made them top the list.

would it be a good idea to exclude packages that has not been updated in the last 1 or 2 years for this py3 readiness list?

also would it be nice to put a different color for those py2 only but has py3 alternative packages? might also list the alternative packages next to it as a reference.

I believe that will make the list much more useful as a reference to new py3 developers

[chhantyal]

Thank you for your input. This is something I am also thinking. See some related discussion on #9