Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
  • 13:44
    Ahmed-Hindy starred pyblish/pyblish
  • Aug 09 09:56
    studiovc starred pyqt/python-qt5
  • Jul 29 09:53
    tdard edited #72
  • Jul 29 09:52
    tdard opened #72
  • Jul 25 16:11
    hannesdelbeke opened #390
  • Jul 25 13:22
    britisharmy starred pyqt/python-qt5
  • Jul 21 22:26
    dependabot[bot] labeled #27
  • Jul 21 22:26
    dependabot[bot] opened #27
  • Jul 21 22:26

    dependabot[bot] on bundler

    Bump tzinfo from 1.2.2 to 2.0.5… (compare)

  • Jul 21 19:10
    gabrieljreed starred pyblish/pyblish-qml
  • Jul 19 06:30
    mottosso commented #43
  • Jul 18 20:19
    Event-Horizon-Labs edited #43
  • Jul 18 20:18
    Event-Horizon-Labs opened #43
  • Jul 11 16:58
    KentMrng starred pyblish/pyblish
  • Jul 11 16:57
    KentMrng starred pyblish/pyblish-base
  • Jul 11 16:57
    KentMrng starred pyblish/pyblish-houdini
  • Jul 11 15:37
    gjeevana27 commented #67
  • Jul 09 21:17
    hannesdelbeke edited #389
  • Jul 09 03:32
    mickey3721 starred pyqt/python-qt5
  • Jul 08 16:43
    hannesdelbeke edited #389
Erik Johansson
it is sooooooo slow
or hmm
now it didnt take long
btw on the action, how do i make the icon turn red if it fails? is it assert False as with validators?
Toke Jepsen
yeah, raising any errors should do it.
assert False, "something" or raise ValueError("something")
Erik Johansson
if i would go about adding more tooltips to the interface to help users
they should go in window.py right?
Toke Jepsen
Hmmm, that is a good point. What kind of tooltips are you wanting? Describing what a plugin does?
Erik Johansson
basically everything that can be clicked
that is an icon
validators i think middle mouse works fine
as the text can be kinda long
Toke Jepsen
Yeah, that would be in window. Might be wrong though @mottosso ?
For plugins middle mouse would work, but a perspective view would be better :)
Marcus Ottosson
window.py is the catch-all for graphics at the moment
I'd start there
As it grows, have a think about which parts you think belong together, and are enough of, to potentially get separated into its own module
Marcus Ottosson

But yes, a Perspective is what's missing

For reference, here's the design document for when it was implemented in QML.

  • pyblish/pyblish-qml#79
Erik Johansson
offtopic but anyone know if there is some random chat for python/pipeline stuff on the net that is not a google discussion group
Toke Jepsen
Here? 😀
Erik Johansson
:) didnt know if you wanted it polluted
Toke Jepsen
Think we are all interested in off topic stuff as well. There is also an off topic tag on the Pyblish forums😀
Erik Johansson
so offtopic python question then :)
Tractor got a python module that is very neat
but in the same site-packages folder that it lives also nimby and PySide lives
so if I use PYTHONPATH env variable or sys.path.append i have had some fun issues with mismatching versions of those packages in applications that include them
so the question is basically can you load a module with submodules using imp or importlib by full path
i cant get it to work
can only load single files
[erjo@3d47 ~]$ cd /opt/pixar/Tractor-2.2/lib/python2.7/site-packages
[erjo@3d47 site-packages]$ ls -la
total 20
drwxr-xr-x  7 root root    73 Jan  2  2016 .
drwxr-xr-x 26 root root 12288 Mar 30  2016 ..
drwxr-xr-x  3 root root   136 Jan  2  2016 dateutil
drwxr-xr-x  2 root root   106 Jan  2  2016 nimby
drwxr-xr-x  2 root root  4096 Jan  2  2016 PySide
drwxr-xr-x  2 root root    66 Jan  2  2016 rmanpy
drwxr-xr-x  5 root root    56 Jan  2  2016 tractor
how it looks
Marcus Ottosson
Hey, just saw this
Are you familiar with Ecosystem or Rez?
In a nutshell, they're environment management tools and what they would do, at a practical level, is to put each of those packages in it's own directory, potentially with it's own version number.
In that way, you add each directory to your PYTHONPATH, and can have multiple co-existing versions alongside each other
$ export PYTHONPATH=$(pwd)/PySide_1.21:$(pwd)/tractor_2.5
Alternatively, as a temporary measure, or if you can't alter that directory, then you could add the path to your sys.path, import tractor and then remove the path again.
tractor would remain cached in sys.modules from anywhere else you import it
Erik Johansson
yeah i got my own version of ecosystem for managing different versions and etc
but i want to avoid modifying the default directory structure of tractor
Marcus Ottosson
Ah ok, so it was more specifically about this particular case
Erik Johansson
temporarily adding and removing sounds like it should be doable
yeah this specific case
i'll give that a try
Marcus Ottosson
Sure, I would try the sys.path approach first; you can do it via imp and others, but the import system is complex stuff, I always run into edge cases early when trying to work around it
import sys
sys.path.insert(0, "/path/to/tractor")
import tractor
Erik Johansson
thanks, should work fine, only a couple few places its imported
Marcus Ottosson
If you put it in userSetup.py or the like, you could get away with only doing it once per Python session.