Thank you @lune for the PR!

Thank you @pm990320 for the PR (#234)!

Thank you @whattheserver for the PR (#229)!

Some people ran into a PermissionError: ... create-dmg when running fbs installer on Mac. This was likely because I packaged fbs 0.9.2 on a Windows machine, which must have checked out that file with CRLF line endings. This release should hopefully fix the issue.

Thanks to @whattheserver for the PR (#227)!

fbs Pro supports the latest Python, PyQt and PySide versions. See https://build-system.fman.io/pro.

In particular, fbs installer should work now. Thank you @luigifcruz for the PR!

There are cases where you simply need to supply extra arguments to fbs's invocation of PyInstaller. There is now a new setting, extra_pyinstaller_args, that lets you supply those parameters. For example, in base.json:

{
    ...,
    "extra_pyinstaller_args": [
        "--additional-hooks-dir", "some_hooks",
        "--additional-hooks-dir", "some_more_hooks",
    ]
}

Fixes #157 and #167.

The release command was also improved. You can now use any of the following command lines:

fbs release
fbs release 1.2.3
fbs release current

Fixes #211.

Thank you to @whattheserver and @luigifreitas for their PRs.

pip is now automatically updated to the latest version when you build your app with fbs's Docker integration. See #210. Thank you to @whattheserver for the PR!

See #202. Thank you @josh-richardson for the PR!

Thanks @lune and @komodovaran!

fbs is incompatible with PyInstaller 3.6 (see #169). This release fixes the problem by pinning fbs's required PyInstaller version to 3.4. So when you now do

pip install fbs

Then this installs PyInstaller 3.4 (previously, it installed 3.6).

For instructions, please see the new section on code signing in the Manual.

This is a backwards-incompatible release. To upgrade to it, replace the following import:

from fbs_runtime.application_context import ApplicationContext

by one of the following two:

from fbs_runtime.application_context.PyQt5 import ApplicationContext
# or:
from fbs_runtime.application_context.PySide2 import ApplicationContext

Explanation

Earlier fbs versions had the following code:

try:
    from PyQt5 import ...
except ImportError:
    from PySide2 import ...

This lead to problems when you had both PyQt5 and PySide2 installed:

1. PyInstaller packaged both (!) libraries because it saw both imports.
2. The above made fbs always use PyQt5. But if your app uses PySide2,
   then PySide2 and PyQt5 classes / code would be mixed.
3. It wasn't clear (or deterministic, really) which Python binding took
   precedence. For instance, PyQt5 and PySide2 set different QML search paths.
   See #114.

To fix these problems, the above code was split into separate files: One that
contains all PyQt5 imports, and another that contains all PySide2 imports. You
are supposed to import precisely one of the two. This makes PyInstaller
only package the one necessary library, and prevents the above problems.

Please note that actually, PyInstaller 3.4 is not yet smart enough to do 1).
However, recent development versions of it (eg. revision 9e1f05ba2) can do this.

Until PyInstaller 3.5 is out, the best workaround to avoid all of these problems
is to simply not have both PyQt5 and PySide2 installed in your virtual environment
when using fbs.

See #112.

See #89 and #53. Instead of the exceptions mentioned there, fbs now says "Your Linux distribution is not supported, sorry. You can run fbs buildvm followed by fbs runvm to start a Docker VM of a supported distribution."

Fixes #109

The error was:

iconutil[2088] <Error>: ImageIO: _CGImageDestinationCreateWithWriter capacity parameter (14) is too large for this file format (max is 10)