Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 25 16:37
    Pandinosaurus starred pyqt/python-qt5
  • Nov 25 09:35
    megies commented #73
  • Nov 25 09:34
    megies commented #73
  • Nov 24 14:43
    megies closed #73
  • Nov 24 14:43
    megies commented #73
  • Nov 18 11:09
    mottosso commented #389
  • Nov 17 16:58
    hannesdelbeke edited #389
  • Nov 17 16:55
    hannesdelbeke edited #389
  • Nov 17 16:54
    hannesdelbeke edited #389
  • Nov 17 16:54
    hannesdelbeke edited #389
  • Nov 17 14:38
    hannesdelbeke edited #389
  • Nov 17 14:36
    hannesdelbeke edited #389
  • Nov 17 14:35
    hannesdelbeke edited #389
  • Nov 17 14:34
    hannesdelbeke edited #389
  • Nov 17 14:33
    hannesdelbeke edited #389
  • Nov 17 14:33
    hannesdelbeke edited #389
  • Nov 17 14:20
    hannesdelbeke edited #389
  • Nov 17 14:20
    hannesdelbeke edited #389
  • Nov 16 12:52
    polythilene starred pyblish/pyblish-base
Toke Jepsen
@tokejepsen

Hey @p4vv37,

There is something wrong with using such high values for the order, but it should support it. I'll make a bug issue about it. If you run the following code with smaller order values, it should output the expected result:

import pyblish.api

items = ["john", "door"]


class CollectInstances(pyblish.api.ContextPlugin):

    order = 0

    def process(self, context):
        for item in items:
            context.create_instance(item)


class PrintInstances(pyblish.api.InstancePlugin):

    order = 1

    def process(self, instance):
        print("Instance is: %s" % instance)

pyblish.api.register_plugin(CollectInstances)
pyblish.api.register_plugin(PrintInstances)

import pyblish.util
context = pyblish.util.publish()
pyblish/pyblish-base#301
Paweł
@p4vv37
It does work now.
But I do not think it is an issue with high numbers: the issue is, that one of the plugins has to have an order of "0".
If You'd set the orders to 1 and 2 it still would not run.
Toke Jepsen
@tokejepsen
Yeah, I've made an issue about it, so we can sort it out asap.
Paweł
@p4vv37
ok, anyway, thank You :)
Toke Jepsen
@tokejepsen
You should be able to continue with learn by example though :) Thanks for bringing this to our attention.
Marcus Ottosson
@mottosso
Thanks @p4vv37, that definitely smells like a problem.
Marcus Ottosson
@mottosso
Hey @p4vv37, I'm curious about your Pyblish_exe project
It looks like what I'm interested in making as well
A self-contained pyblish-qml
Could you tell us a little bit about it? :)
Paweł
@p4vv37
Well, there's not much to talk about, it's just an exe that runs only the server, created with a use of pyinstaller and Python 3.X. I want to run pyblish-qml on different machines which have only Maya's Python 2.7 available, so I thought that distributing such exe and running it from the script that opens the pyblish gui would be the easiest way to achieve this.
Alternatively, I guess, I'd have to install Python 3 on every one of them and then from the maya's python run the server in this other python before opening the gui in maya and that seems a lot more problematic.
Marcus Ottosson
@mottosso
Good thinking
Yes, you could do that; install on every machine
But what most people do, is install PyQt5 on a central location
And point their PYTHONPATHs to it
Or, store the entire Python 3 + PyQt5 centrally, and launch via that one
There's a standalone PyQt5 for Python 2, here: https://github.com/pyqt/python-qt5
Paweł
@p4vv37
Thanks, I'll check it
Marcus Ottosson
@mottosso
Hi @p4vv37, the bug you reported has now been fixed; it was a problem with the documentation, from 4 to 11 if you'd like to take another look at those.
Erik Johansson
@Eiken
simple question of the day probably
after running an action the validator is still red
even if the action succedes at fixing the issue
any way to make it green so you dont have to refresh and rerun validation?
Toke Jepsen
@tokejepsen
Do you have an action icon?
Erik Johansson
@Eiken
yes, the action icon turns green
Toke Jepsen
@tokejepsen
Just so I know the use case, you want to
  1. Validate first.
  2. Run actions that fixes the validation issues.
  3. Continue the publish.
    Is that right?
Erik Johansson
@Eiken
yeah
it seems to confuse artists that they need to redo it all after fixing something
but it kinda makes sense as the fix might make other things not validate
i might just have to inform them more
Toke Jepsen
@tokejepsen
Yeah, the problem is that running actions isn't a guarantee that the validation issues are fixed.
Found lots of times, especially when introducing new validators, that there are edge case that the actions didn't account for, but the validator did.
Toke Jepsen
@tokejepsen
This might be overkill but interesting. If we somehow saved the context before validation, we could essentially revalidate single validators after an action is run.
Marcus Ottosson
@mottosso
Having the option to run individual validators at will is a great goal I think
There is nothing stopping that technically, its purely a UI issue
Toke Jepsen
@tokejepsen
Yeah, you could keep the context in memory until reset, right?
Marcus Ottosson
@mottosso
Sure could
Technically forever, but GUIs generally make a new one on reset
Toke Jepsen
@tokejepsen
Forever would also be a memory hog, I guess.
Erik Johansson
@Eiken
totally offtopic but anyone know a fast way to do mc.polyMoveVertex(s, constructionHistory=False)
it is sooooooo slow
or hmm
now it didnt take long
what
btw on the action, how do i make the icon turn red if it fails? is it assert False as with validators?
Toke Jepsen
@tokejepsen
yeah, raising any errors should do it.
assert False, "something" or raise ValueError("something")
Erik Johansson
@Eiken
if i would go about adding more tooltips to the interface to help users
they should go in window.py right?