| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
And avoid confusion with bugs who's shorname is `list'? ;)
Now the usage info and help string also reflect the new method.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From his Wed, 24 Jun 2009 23:08:25 +0200 email to the list:
Hello
As I noted some time ago, there is not a way to list all the present targets
in the current repository.
At the time, Chris send me a patch to have this feature, but it still not
merged in the last revision (314).
So this is a patch for this feature to apply against revision 314. It is
basically a port of the old Chris's patch.
bye
Gianluca
|
|
|
|
|
|
|
|
|
|
|
| |
Also added libbe.bug.cmp_last_modified, which handles part of
9ce2f015-8ea0-43a5-a03d-fc36f6d202fe. To do better we could extend
the RCS framework.
I also transcribed a few emails from the be-devel list onto their
relavent bugs and closed a few bugs.
Finally, I removed some left over InvalidValue cruft.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Since
<creator>John Doe <jdoe@example.com></creator>
is not valid XML.
|
|/
|
|
| |
Following Chris' advice. Don't know what I was thinking before ;).
|
| |
|
|
|
| |
$ be list --invalid-option | be comment <bug-id> -
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I rewrote a few of his routines, e.g. generalizing
Comment.string_thread to run a caller-specified method avoided the
need for some duplicate code in Comment.xml_thread. There was also a
reasonable reorganization of libbe.settings_object.versioned_property
because the <in_reply_to> field of the Comment.xml output was giving
me `-1' (= old settings_object.EMPTY) instead of None, even after I
had set comm.in_reply_to to None. The rewritten versioned_property
avoids the ambiguity of UNPRIMED vs EMPTY, and avoids the stupididy of
my using EMPTY=-1 ;).
|
| | |
|
| |
| |
| |
| |
| | |
The new setting is currently only used when creating new bugs with
becommand/new.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I also disabled interspersed options and arguments in
cmdutils.CmdOptionParser. See
http://docs.python.org/library/optparse.html
Now
$ be severity xyz --complete
returns available severities. It had previously returned
--help --complete
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
becommands/severity gets the configured settings appropriately.
Todo:
adjust setting-validation to compare against the current values.
setup becommands/severity to --complete severities.
|
| |
| |
| |
| |
| |
| |
| | |
They currently have no effect, but you can see them with
$ be set
There's a lot of information in this one 'settings' variable. I think
set will have to be specialized to handle arrays smoothly...
|
| |
| |
| |
| | |
Closes e2f6514c-5f9f-4734-a537-daf3fbe7e9a0
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
settings_object.SavedSettingsObject encapsulates some of the common
settings functionality in the BE BugDir, Bug, and Comment classes.
It's a bit awkward due to the nature of scoping in python subclasses,
but it's better than reproducing this code in each of the above classes.
Now I need to move Bug and Comment over to *this* system ;).
|
| |
| |
| |
| | |
The code is a bit uglier now, but it's a good deal faster :).
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Now most of the bug-id arguments support Bash completion. Since there
will hopefully be lots of bugs in the database, I decided to filter
the list of available bugs. Currently, we just auto-complete active
bugs for most commands, with the exceptions of open (obviously) and
status (which needs to work on all types of bugs).
|
| |
| |
| |
| |
| |
| |
| |
| | |
All the other commands currently use default_complete(), which has no
effect other than catching the --complete option and effectively
aborting execution.
This closes 8e1bbda4-35b6-4579-849d-117b1596ee99
|
| | |
|
| |
| |
| |
| | |
I'm still working on a clean implementation though...
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I borrowed most of the code for this.
get_encoding() is from Trac
http://trac.edgewall.org/browser/trunk/trac/util/datefmt.py
format_datetime()
Trac has a BSD license
http://trac.edgewall.org/wiki/TracLicense
I don't know if such a small snippet requires us to "reproduce the
above copyright" or where we need to reproduce it if it is needed.
The stdout/stdin replacement code follows
http://wiki.python.org/moin/ShellRedirectionFails
Because of the stdout replacement, the doctests executes now need an
optional 'test' argument to turn off replacement during the doctests,
otherwise doctest flips out (since it had set up stdout to catch
output, and then we clobbered it's setup).
References:
http://wiki.python.org/moin/Unicode
http://www.amk.ca/python/howto/unicode
http://www.python.org/dev/peps/pep-0100/
I also split libbe/editor.py off from libbe.utility.py and started
explaining the motivation for the BugDir init flags in it's docstring.
|
| |
| |
| |
| |
| |
| | |
The situation really calls for a global encoding setting rather than
lots of hardcoded "utf-8"s. See bug
f7ccd916-b5c7-4890-a2e3-8c8ace17ae3a
|
| | |
|
| | |
|
|/
|
|
|
| |
Kindof a cludgy check, but there's currently no simpler way to find
valid entries for a given setting name (that I can think of).
|
|
|
|
| |
I tried to stick to CAPS for argument placeholders.
|
|
|
|
|
| |
Also emptied becommands/__init__.py. I didn't understand the plugin
interface when I wrote it.
|
|
|
|
| |
Also added blank lines to separate the new/modified/removed groups.
|
|
|
|
| |
Fixes bug b3c6da51-3a30-42c9-8c75-587c7a1705c5
|
| |
|
|
|
|
| |
Also some minor cleanups.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I pushed a lot of the little helper functions into the main classes,
which makes it easier for me to keep track of what's going on. I'm
now at the point where I can run through `python test.py` with each of
the backends (by changing the search order in rcs.py
_get_matching_rcs) without any unexpected errors for each backend
(except Arch). I can also run `test_usage.sh` without non-Arch errors
either.
However, don't consider this a stable commit yet. The bzr backend is
*really*slow*, and the other's aren't blazingly fast either. I think
I'm rewriting the entire database every time I save it :p. Still, it
passes the checks. and I don't like it when zounds of changes build up.
|
| |
|
| |
|
|
|
|
|
| |
Also removed explicit comparisons from beweb/controllers.py, since
they are now built into the Bug.__cmp__ method.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Lots of changes and just one commit. This started with bug
dac91856-cb6a-4f69-8c03-38ff0b29aab2, when I noticed that new bugs
were not being added appropriately with the Git backend. I'd been
working with Git trouble before with bug
0cad2ac6-76ef-4a88-abdf-b2e02de76f5c, and decided things would be
better off if I just scrapped the current RCS architecture and went to
a more object oriented setup. So I did. It's not clear how to add
support for an RCS backend:
* Create a new module that
- defines an inheritor of rsc.RCS, overriding the _rcs_*() methods
- provide a new() function for instantizating the new class
- defines an inheritor of rcs.RCStestCase, overiding the Class attribute
- defines 'suite' a unittest.TestSuite testing the module
* Add your new module to the rest in rcs._get_matching_rcs()
* Add your new module to the rest in libbe/tests.py
Although I'm not sure libbe/tests.py is still usefull.
The new framework clears out a bunch of hackery that used to be
involved with supporting becommands/diff.py. There's still room for
progress though. While implementing the new verision, I moved the
testing framework over from doctest to a doctest/unittest combination.
Longer tests that don't demonstrate a function's usage should be moved
to unittests at the end of the module, since unittest has better
support for setup/teardown, etc.
The new framework also revealed some underimplented backends, most
notably arch. These backends have now been fixed.
I also tweaked the test_usage.sh script to run through all the backends
if it is called with no arguments.
The fix for the dac bug turned out to be an unflushed file write :p.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Using the __desc__ reduces documentation duplication. It's also better
than using __doc__, because __doc__ could (should?) be more than one-line
long, and we just want a short description to jog our memories in the
complete command list.
Also moved unique_name from cmdutil.py to names.py to avoid the
bug->cmdutil->bugdir->bug
cyclic include.
|
| |
|