Skip to content

dreua/portingdb

 
 

Repository files navigation

A database of packages that need porting to Python 3, and tools to manage it.

This software is a mess. It was created for one purpose and was expected to not be needed soon. Meanwhile, hacks are piling on.

Deployed report

A HTML report is located at:

http://fedora.portingdb.xyz/

Unless you want to refresh data there, or run additional reports, you can just look at that.

Installation

This software is not released. To install it, first set up a Python virtual environment. Then run directly from Git working directory:

(venv) $ python -m pip install -r requirements.txt

Usage

First, you will need to load a database.

(venv) $ python -m portingdb --datadir data/ load

This will create a portingdb.sqlite file in the current directory. Currently, the database needs re-loaded every time the data changes. (If the schema changes, you will need to delete the portingdb.sqlite file before re-loading data.)

To check the database, do:

(venv) $ python -m portingdb status

To start a HTML report server, start:

(venv) $ export PYTHONPATH=.
(venv) $ python -m portingdb serve

Check drops

There is a script that checks what python2 packages can be dropped from Fedora during the Mass Python 2 Package Removal.

Run it with:

(venv) $ python -m portingdb --datadir data/ check-drops

See the docstring of portingdb/check_drops.py for more info.

Freezing

A static website with the HTML repot can be build by:

(venv) $ export PYTHONPATH=.
(venv) $ python elsasite.py freeze

You can add --serve for he freeze command to immediately inspect the result.

Contribute

License

This code is under the MIT license. May it serve you well.

About

Database & tools to track the Python3 porting effort

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Python 67.3%
  • HTML 28.5%
  • JavaScript 3.1%
  • Shell 1.1%