I’m about to perform some major refactoring to the GitHub layout of this project, based on feedback from @jedfrechette in one of the issues in pyblish-win, read more here
I expect to have a working version ready by the end of today, so this shouldn’t have much of an effect on anyone; but there will be problems.
What will happen?
Repositories will have their name changed.
The goal is to make
pyblish/pyblish the official sum of all supported sub-projects, such as the integrations into hosts, the GUI and such; just as
pyblish-x is today.
Due to how versioning works today.
The base Pyblish library has a version which other projects must adhere to, but distributions at the same time have their own independent version, due to how their layout and feature set can update without necessarily changing things up-stream; such as a bugfix to the Windows distribution of PyQt5.
The primary difference once renovation is complete, is that
pyblish/pyblish will have a version number, and aggregrations such as
pyblish-win will inherit this number plus a “build” number.
- pyblish 1.3.0
- pyblish-win 1.3.0-build1
This is the tricky part.
I’ll just rename the GitHub repos, which is simple enough, but what will happen is that external services such as Travis-CI will break, external links to Pyblish, such as those on Tech-Artists.org or CGTalk or Wiki’s might refer to things wrongly but perhaps most importantly, the installation procedure of for example
pyblish-win will likely break until it has been updated.
pyblish-win will also eventually see it’s name changed to better reflect it’s purpose as a distribution, as opposed to an extension or integration which its name currently suggests.
What will remain unchanged however is the binary installer for Windows, so if you have just arrived to the Pyblish scene and are looking to get started, you can find the installer here.
Let the battle begin!
Will the import path change?
No, you will still import like this:
pyblish-base is only visible and relevant on GitHub.
Can I still install via pip?
Yes, installation remains unchanged.
$ pip install pyblish
Here are some of the tests I’ve run with this new configuration in place.
pip install pyblish -- OK pyblish-win/install.bat -- OK pyblish-win-setup.exe` -- OK travis -- OK coveralls.io -- OK appveyor -- OK wiki -- OK developer guide -- OK pyblish by example -- OK
To the reader; if you spot any references to
pyblish-x, please let me know as soon as possible as that is henceforth a bug in the documentation.