>
>
> Got it figured thanks for the help. Pretty simple really, in my code I'll
> just run the following:
> import logging
> logging.getLogger()
> logger.setLevel(logging.DEBUG)
>

glad you fixed the problem. i'm surprised that that *stops* the messages?
 seems like it would make it more verbose.  are you using the logger
anywhere?

-chad




>
> seems to work in the short term.
>
> Cheers,
> Shawn
>
>
>
> On Thu, Apr 14, 2011 at 10:37 AM, Chad Dombrova <[email protected]> wrote:
>
>>
>>> Thanks for the info, I've tried searching the docs for any info on the
>>> logging module, is there any documentation I also have plogging.py that I
>>> can look through.
>>>
>>
>> plogging is pymel's logging module, that makes use of the standard python
>> logging library: http://docs.python.org/library/logging.html
>>
>> because logging is a standard library, different apps using the logging
>> module in a common python session can effect each other, either
>> intentionally or unintentionally.
>>
>> -chad
>>
>>
>>
>>>
>>> Cheers,
>>> Shawn
>>>
>>> On Wed, Apr 13, 2011 at 8:38 PM, Chad Dombrova <[email protected]>wrote:
>>>
>>>>  >
>>>> > I'm using the SUDS client to connect. Anyone have any idea where to
>>>> > start on this one?
>>>>
>>>> i'm guessing that the logger might have something to do with it.  pymel
>>>> sets up at least one logger (can't remember offhand if it's the root 
>>>> logger)
>>>> to print to the script editor, and maybe JIRA's logger is inheriting this.
>>>>  either that or JIRA is setting changing the verbosity of the logger.   you
>>>> can try editing pymel.conf to change the logger settings, or use the 
>>>> logging
>>>> module to get more control.
>>>>
>>>> -chad
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> http://groups.google.com/group/python_inside_maya
>>>>
>>>
>>>  --
>>> http://groups.google.com/group/python_inside_maya
>>>
>>
>>
>

-- 
http://groups.google.com/group/python_inside_maya

Reply via email to