Thanks to a bug report in GitHub, it was pointed out that 0.10.0 fails to
pip install from PyPI due to some necessary files (namely the man files)
not being packaged. A new version, 0.10.1, has been tagged with the
necessary fixes.

Sean

On Tue, Jul 7, 2015 at 10:07 PM, Sean Vig <[email protected]> wrote:

> Hi everybody,
>
> I'm happy to announce the 0.10.0 release of Qtile. This release is
> primarily to address the incompatibility with the most recent versions of
> cffi, cairocffi, and xcffib. If you need a version of qtile capable of
> running cffi <= 1.0, you can run qtile-0.9.x, cairocffi-0.6, and
> xcffib-0.2.x. A warning to those updating that xcffib *must* be installed
> before cairocffi to properly build the cffi module, you will be warned at
> install time if this is a problem with instructions on how to fix your
> installation.
>
> There is a host of new widgets, improvements, and bugfixes, a summary of
> which can be read on the changelog here:
>
> https://github.com/qtile/qtile/blob/develop/CHANGELOG#L1
>
> One thing to note in particular is that there are some previously
> deprecated things that we have removed. Unfortunately, deprecation warnings
> were not printing to logs (a bug that has since been fixed), so this may
> break some configurations without warning.
> <https://github.com/qtile/qtile/blob/develop/CHANGELOG#L1>
>
> Thank you to everyone who reported problems, added features, fixed bugs,
> and helped in testing this release. There are likely to be some problems
> with the new cffi changes, and we are working to make that smoother, so any
> feedback is greatly appreciated!
>
> Sean
>
> P.S.: A belated but resounding thanks to Tycho for all the work he did
> managing Qtile to get to this point! With your knowledge and engagement on
> the mailing list and IRC, you remain an invaluable resource to this project
>

-- 
You received this message because you are subscribed to the Google Groups 
"qtile-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to