python-bugzilla

python-bugzilla@lists.fedorahosted.org

137 discussions

ANNOUNCE: python-bugzilla 2.1.0 released
by Cole Robinson 31 Mar '17

31 Mar '17

I'm happy to announce a new release of python-bugzilla, version 2.1.0. python-bugzilla is a library and commandline tool for interacting with a bugzilla instance, including querying, modifying, and creating bug reports. The release can be downloaded from: https://github.com/python-bugzilla/python-bugzilla/archive/v2.1.0.tar.gz https://pypi.python.org/pypi/python-bugzilla/2.1.0 This release includes: - Support for bugzilla 5 API Keys (Dustin J. Mitchell) - bugzillarc can be used to set default URL for the cli tool - Revive update_flags wrapper - Bug fixes and minor improvements Thanks to everyone who has contributed to this release through testing, bug reporting, submitting patches, and otherwise sending in feedback! Thanks, Cole

1 0

updating needinfo flag with 2.0.0
by Dennis Kliban 28 Mar '17

28 Mar '17

The following code used to work with python-bugzilla 1.2, but has stopped working with 2.0.0. BZ.update_flags(bug.id, [{ "name": "needinfo", "status": "?", "requestee": needinfo_email, "new": True}]) The new Bug.updateflags() method seems to only handle flags with a simple status. How do I set a needinfo flag using 2.0.0? Thanks, Dennis

3 3

Release of 2.1.0 with api key support?
by Dustin Mitchell 01 Mar '17

01 Mar '17

Hi -- I'd like to update bugwarrior, which uses python-bugzilla, to support API keys. To do so, I need the newer version of python-bugzilla released. Any chance we could get a 2.1.0 with that feature included? Dustin

2 1

Re: Failing on login to company bugzilla
by Cole Robinson 21 Feb '17

21 Feb '17

On 02/19/2017 12:10 AM, 明 wrote: > Hi specialists, > > I'm trying to use python-bugzilla 2.0 to do a saved query, I imitated the > example to make up a small code snippet like below: > -------------------------------------------------------------------- > #!/usr/bin/env python > # encoding: utf-8 > > from __future__ import print_function > import time > import bugzilla > > # public test instance of bugzilla.redhat.com <http://bugzilla.redhat.com>. > It's okay to make changes > login_URL = "https://bugzilla.mycompany.com/index.cgi" This looks incorrect, you should point to xmlrpc.cgi, not index.cgi - Cole > URL = > "https://bugzilla.mycompany.com/buglist.cgi?cmdtype=runnamed&namedcmd=triagi…" > bzapi = bugzilla.Bugzilla(login_URL, user='xxx', password='xxxxx') > > > query = bzapi.url_to_query(URL) > query["include_fields"] = ["id", "summary"] > bugs = bzapi.query(query) > print("The URL query returned %d bugs" % len(bugs)) > ----------------------------------------------------------------------------- > > > But I always got such errors in my macbook env: > ============================================ > mingMBA:python-buzilla mingli$ python query.py > Traceback (most recent call last): > File "query.py", line 11, in <module> > bzapi = bugzilla.Bugzilla(login_URL, user='xxx', password='xxxxx') > File "build/bdist.macosx-10.12-intel/egg/bugzilla/base.py", line 289, in > __init__ > File "build/bdist.macosx-10.12-intel/egg/bugzilla/base.py", line 508, in connect > File "build/bdist.macosx-10.12-intel/egg/bugzilla/base.py", line 556, in login > File "build/bdist.macosx-10.12-intel/egg/bugzilla/base.py", line 525, in _login > File > "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xmlrpclib.py", > line 1240, in __call__ > return self.__send(self.__name, args) > File "build/bdist.macosx-10.12-intel/egg/bugzilla/transport.py", line 88, in > _ServerProxy__request > File > "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xmlrpclib.py", > line 1599, in __request > verbose=self.__verbose > File "build/bdist.macosx-10.12-intel/egg/bugzilla/transport.py", line 183, > in request > File "build/bdist.macosx-10.12-intel/egg/bugzilla/transport.py", line 174, > in _request_helper > bugzilla.transport.BugzillaError: not well-formed (invalid token): line 66, > column 97 > =========================================================== > > It's seems my user or password string's format not correct? > Is this related to the env that I use company's proxy to connect company > network from home? > > Very expecting your reply! > > Thanks, > Ming

1 0

script stopped working after upgrading to 2.0.0
by Dennis Kliban 17 Feb '17

17 Feb '17

I have some code that looks very similar to what I have below. from bugzilla.rhbugzilla import RHBugzilla BUGZILLA_URL = 'https://bugzilla.redhat.com' BZ = RHBugzilla(url='%s/xmlrpc.cgi' % BUGZILLA_URL, user=user, password=password) bugzilla_bugs = BZ.query(RHBugzilla.url_to_query(non_closed_bug_with_ext_tracker)) for bug in bugzilla_bugs: for external_bug in bug.external_bugs: print external_bug This works fine with python-bugzilla 1.2.2, but when switching to 2.0.0, I get an exception like this: Traceback (most recent call last): File "pulp_packaging/ci/redmine_bugzilla.py", line 242, in <module> main() File "pulp_packaging/ci/redmine_bugzilla.py", line 193, in main for external_bug in bug.external_bugs: File "/usr/lib/python2.7/site-packages/bugzilla/bug.py", line 110, in __getattr__ raise AttributeError(msg) AttributeError: Bug object has no attribute 'external_bugs'. Does anyone have a suggestion for how to fix my script? Thanks, Dennis

2 3

python-bugzilla-2.0.0: Traceback on connect
by Lukas Zachar 16 Feb '17

16 Feb '17

Hi Cole and all, Before filling bug I'd like to check whether there is an PEPKAC or not. Following code stopped working after I've updated from python-bugzilla-1.2.2-4.fc25 to python-bugzilla-2.0.0-1.fc25 from bugzilla import Bugzilla BUGZILLA_URL = "https://bugzilla.redhat.com/xmlrpc.cgi" bz = Bugzilla(url=BUGZILLA_URL) bz.connect(BUGZILLA_URL I've run bugzilla login before, bugzilla binary seems to work correctly. What am I doing wrong? The error looks like it is a server side issue. Thanks for any hints. If necessary I'll open bug ;) Traceback is Traceback (most recent call last): File "repro.py", line 5, in <module> bz.connect(BUGZILLA_URL) File "/usr/lib/python2.7/site-packages/bugzilla/base.py", line 489, in connect if self._proxy: File "/usr/lib64/python2.7/xmlrpclib.py", line 1243, in __call__ return self.__send(self.__name, args) File "/usr/lib/python2.7/site-packages/bugzilla/transport.py", line 88, in _ServerProxy__request ret = ServerProxy._ServerProxy__request(self, methodname, params) File "/usr/lib64/python2.7/xmlrpclib.py", line 1602, in __request verbose=self.__verbose File "/usr/lib/python2.7/site-packages/bugzilla/transport.py", line 183, in request return self._request_helper(url, request_body) File "/usr/lib/python2.7/site-packages/bugzilla/transport.py", line 169, in _request_helper raise sys.exc_info()[1] xmlrpclib.Fault: <Fault Client: "Can't locate .pm in @INC (@INC contains: /var/www/html/bugzilla/extensions CODE(0x7f971c1f7f68) CODE(0x7f971c1aeb68) CODE(0x7f971c0dfa58) CODE(0x7f971c0d6010) CODE(0x7f971c8671a8) CODE(0x7f971c825960) CODE(0x7f971ccf3730) CODE(0x7f971ccf2e60) CODE(0x7f971cc04fc8) CODE(0x7f971d599860) CODE(0x7f971d4aa200) CODE(0x7f971d96f550) CODE(0x7f971d967ed0) CODE(0x7f971d967498) CODE(0x7f971d93ffc8) CODE(0x7f971d8a8298) CODE(0x7f971d933850) CODE(0x7f971d833228) CODE(0x7f971d822348) CODE(0x7f971d7d1a70) CODE(0x7f971c310a70) CODE(0x7f971b741878) /var/www/html/bugzilla/lib /var/www/html/bugzilla /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 /etc/httpd) at /var/www/html/bugzilla/Bugzilla/WebService/Server/XMLRPC.pm line 79.\n"> -- Lukas Zachar BaseOS QE - Apps lzachar: #brno, #urt, #qa

2 2

Attempting to query Red Hat's internal bugs
by Pavel Zagalsky 09 Feb '17

09 Feb '17

Hey there! I am writing a Telegram Bugzilla bot based on Python Bugzilla and I am trying unsuccessfully to fetch RH's internal bugs and all I get are the upstream ones. I am using my account to log in.. What am I doing wrong? Thanks! Pavel

2 4

ANNOUNCE: python-bugzilla 2.0.0 released
by Cole Robinson 08 Feb '17

08 Feb '17

I'm happy to announce a new release of python-bugzilla, version 2.0.0. python-bugzilla is a library and commandline tool for interacting with a bugzilla instance, including querying, modifying, and creating bug reports. The release can be downloaded from: https://github.com/python-bugzilla/python-bugzilla/archive/v2.0.0.tar.gz https://pypi.python.org/pypi/python-bugzilla/2.0.0 This release contains several small to medium API breaks. I expect most users won't notice any difference. I previously outlined the changes here: https://lists.fedorahosted.org/archives/list/python-bugzilla@lists.fedoraho… The major changes are: - Several fixes for use with bugzilla 5 - Bugzilla.bug_autorefresh now defaults to False - Credentials are now cached in ~/.cache/python-bugzilla/ - bin/bugzilla was converted to argparse - bugzilla query --boolean_chart option is removed - Unify command line flags across sub commands Thanks to everyone who has contributed to this release through testing, bug reporting, submitting patches, and otherwise sending in feedback! Thanks, Cole

1 0

Can't access internal Red Hat bugs with Python Bugzilla
by pzagalsk＠redhat.com 05 Feb '17

05 Feb '17

Hey there! I am writing a Telegram Bugzilla Bot and I am trying to fetch internal Red Hat bugs and for some reason I faill.. All my queries are the upstream bugs which are nice but not exactly what I'm looking for. Anybody's available to give me a hand? Thanks! Pavel

1 0

python-bugzilla API changes in git
by Cole Robinson 09 Aug '16

09 Aug '16

Hi all, I've made a number of API changes to python-bugzilla in git. Most of it is removing old mis-designed features which I don't think anyone is actually using. I went through all apps I know of that use python-bugzilla (fedora bits like bodhi pkgdb infra scripts, bugwarrior, searchcode.com) to confirm as much and I don't think anything below will affect them. Even if there's no complains I won't cut the release for 4-6 weeks. The list is long but most changes are fairly straight forward. If any of this sounds controversial, or if I misjudged one of the 'unused' bits and should reconsider, please leave your thoughts. The interesting change is: * Bugzilla.bug_autorefresh now defaults to False. Previously if trying to access Bug.foo, and 'foo' wasn't cached, the Bug() object would basically do a Bug.refresh() and fetch all the bug contents from the server. This default sucks, it can lead to poorly performing scripts and unnecessary bugzilla load. If you have code that uses include_fields, exclude_fields, or extra_fields anywhere, this change may affect you. You can set Bugzilla().bug_autorefresh = False before doing any bug lookup to force this off (with current versions) and catch any errors. If you hit issues you probably need to extend your include_fields specifications. The reason for this change is that the old pattern made it too easy for people's scripts to unintentionally start requiring a much higher number of XMLRPC calls, thus completely negating the usage of include_fields in the first place. Some more details over here: https://github.com/python-bugzilla/python-bugzilla/blob/master/examples/bug… https://bugzilla.redhat.com/show_bug.cgi?id=1297637 These are slightly interesting and may impact a few people: * Credentials are now cached in ~/.cache/python-bugzilla/. If the old ~/.bugzilla{cookies,token} files are in place we will continue to update and use them. * RHBugzilla.rhbz_back_compat __init__ attribute is gone. If the user manually set this to true, we would alter some Bug fields returned via query() to convert python lists into a single comma separated string, to match rhbugzilla output from before the 2012 upgrade. Convert your code to use the modern bugzilla list output. * bin/bugzilla was converted to argparse, which has a bug on python 2.7 that affects some possible command lines: http://bugs.python.org/issue9334 If you use a command like 'bugzilla modify --cc -foo(a)example.com' to remove that email from the CC list, you now need to ensure there's an equals sign in there, like --cc=-foo(a)example.com. That is backwards compatible with old python-bugzilla too, so update your scripts now. A few other options except that format too. * bugzilla query --boolean_chart option is removed. It provided a custom specification for crafting complex queries, similar to what the bugzilla UI can do. I don't think anyone is really using this, but if you are, generate a web query URL and pass it to bugzilla query --from-url '$URL' which is much easier to deal with. * bugzilla query 'boolean' options, where you could say 'bugzilla query --keywords 'foo & bar' to match both substrings, are no longer supported. If you need logic like this, use the --from-url technique mentioned above. * Bug.get_history() is now Bug.get_history_raw() Bugzilla.bugs_history is now Bugzilla.bugs_history_raw() This API is only a year old and unwisely returns raw output from bugzilla, which has some formatting oddities. I renamed it to *_raw so we have the future opportunity to add an API with better output. * The getbugsimple and getbugssimple APIs were removed. They were basically just wrappers around standard getbug() at this point. Use getbug/getbugs instead. * The simplequery API was removed. This basically matches the basic query from the bugzilla front page. Just use the standard query methods instead, see examples/query.py from git. I didn't find any users of this function. * Various whiteboard editing functions from the Bug object were removed. - getwhiteboard: this is just a wrapper around standard Bug attributes - appendwhiteboard, prependwhiteboard, setwhiteboard: these were just wrappers around standard build_update/update_bugs - addtag/gettags/deltag which minor wrappers around the *whiteboard functions, and were poorly named, given that there's an actual bug 'tags' field at this point. See examples/modify.py from git for examples of using the standard update APIs. That said I've never heard of anyone actually using these, and they were designed around really old RHBZ APIs. These I doubt will actually affect anyone: * Bugzilla.initcookie() dropped... use Bugzilla.cookiefile = X instead * Bugzilla.adduser() dropped... it was the same as Bugzilla.createuser * RHBugzilla.multicall __init__ attribute is gone. It's been a no-op and raises a warning for a long time. * Bugzilla.version string is gone... this was meant to describe the python-bugzilla API version but was never used. * Initing like Bugzilla() with no options was previously allowed, but now requires an explicit Bugzilla(url=None). * We no longer handle cookies in LWP format. We've been silently converting them to mozilla format for 2 years so I assume this doesn't affect anyone, but if it does, you might need to delete your caches in ~/.bugzilla{cookies,token} * Bug.setstatus(), Bug.close() args 'private_in_it' and 'nomail' were removed: they have been no-ops for years * Bug.addcomment() args 'timestamp', 'bz_gid' and 'worktime' were removed: they've been no-ops for years * Bug.setassignee() arg 'reporter' was removed: it's thrown an error for years Thanks, Cole

3 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

python-bugzilla