Skip to content

TL;DR

Fext differs in certain aspects due to its indirect usage of Python through auxiliary commands. While it maintains backward compatibility, its adherence to PEP standards remains its primary focus.

Packages directory

Fext uses per user site-packages directory, instead of global site-packages. There are a number of reasons for this:

  • Reduce conflicts between package managers
  • Difficulties in obtaining a global directory

Without legacy support

Fext was originally conceived as a modern and convenient package manager. It does not seek to support outdated projects. There is a PIP for this. Based on this, Fext doesn't support:

The project is still in development and does not have a stable version.