Aqtinstall

Latest version: v3.2.1

Safety actively analyzes 723217 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 12 of 17

0.9.0b3

Not secure
===========================

Changed
-------

* Patch qmake when finishing installation.(100)
qmake has a hard-coded prefix path, and aqt modify binary in finish phase.
it is not necessary for Qt 5.14.2, 5.15.0 and later.
This behavior try to be as same as a Qt installer framework doing.
* Patch Framework.QtCore when finishing installation.(100)
As same as qmake, framework also has a hard-coded prefix path.
(Suggestions from agateau)

0.9.0b2

Not secure
===========================

Added
-----

* CLI: '--archives' option: it takes multiple module names such as qtbase, qtsvg etc.
This is an advanced option to specify subset of target installation.
There is no guarantee it works. It is not recommended if you are unknown what is doing.

0.9.0b1

Not secure
===========================

Added
-----

* Support installation of Qt version for msvc2019
* Add knowlege of components combination on 5.14 and 5.15

Changed
-------

* Show detailed diagnose message when error happend.
* CI test with Qt 5.14.2 and 5.15.0
* CI test with installed mingw tools compiler.
* Depends on py7zr v0.7.0b2 and later.

Fixed
-----

* Tools: Fix mingw installation failure.
* Fix --outputdir behavior about path separator on windows

0.8

Not secure
=======================

Fixed
-----

* docs: fix broken link for qli-installer

0.8b1

Not secure
=========================

Added
-----

* Support specifing config with environment variable AQT_CONFIG

Fixed
-----

* Fix to use concurrency settings

0.8a4

Not secure
=========================

Fixed
-----

* Import-metadata package is required in python version < 3.8 not 3.7.
* Refactoring redirect helper function to improve connection error checks and error message.(109)

Page 12 of 17

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.