aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Added test_usage.sh pointer to the README.W. Trevor King2008-11-191-1/+1
|
* Removed libbe/tests.pyW. Trevor King2008-11-191-31/+0
| | | | | | Not needed with stronger test.py. It's only use would be testing an installed libbe in place... Maybe that is useful enough? If so, we can bring it back.
* One of my tests left my bzr name as John Doe. Seems to be fixed now.W. Trevor King2008-11-181-1/+1
| | | | | | | | | | | I checked with $ python test.py ... $ ./test_usage.py ... $ hg showconfig | grep ui.username && bzr whoami $ git config user.name && git config user.email && tla my-id
* Major rewrite of RCS backends. RCS now represented as a class.W. Trevor King2008-11-1839-773/+1337
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Added 'hg', 'arch', and 'none' RCS modes to test_usage.sh.W. Trevor King2008-11-161-3/+17
|
* Fixed another bug in git.strip_git() (bug 0cad).W. Trevor King2008-11-164-8/+69
| | | | | Also added git mode to test_usage.sh. I'll go through and add modes for the other RCSs...
* Oops, I'd forgotten to tell bzr about my becommands/remove.py.W. Trevor King2008-11-161-0/+58
|
* Merged in my git.py changed fixing Hubert Chathi's git set-root bug (0cad).W. Trevor King2008-11-1610-2/+215
|\
| * Oops... *Now* I've fixed 0cadW. Trevor King2008-11-133-1/+49
| |
| * Fixed 0cad bug with smaller fix.W. Trevor King2008-11-134-2/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Hubert Chathi's fix was confusing for me, so I made a simpler change. Seems to work so far. The problem was that os.path.dirname('filename') returns an empty string ('') if there are no directories in the filename. So when `git rev-parse --git-dir` returned '.git', os returned ''. Later programs didn't recognize '' as a valid directory and crashed. My fix returns '.' in this case, so we don't crash, and avoid having to use full paths. I'm not sure why I don't want to use full paths; they just give me bad vibes...
| * Added Hubert Chathi's git set-root bug report.W. Trevor King2008-11-135-0/+140
| | | | | | | | | | | | | | | | | | | | | | Bug report patch from http://void.printf.net/pipermail/be-devel/attachments/20080623/49500aaf/0cad.bin Reporting thread [Be-devel] Re: set-root in git repository fails Hubert Chathi hubert at uhoreg.ca Tue Jun 24 03:49:23 BST 2008 http://void.printf.net/pipermail/be-devel/2008-June/000038.html
| * Merge from main branchW. Trevor King2008-11-130-0/+0
| |\
| * | Updated imports to handle Python 2.5 ElementTree module.W. Trevor King2008-11-135-2/+115
| | | | | | | | | | | | Opened, fixed, and closed as bug 31c.
| * | Created bug c4e. Wrote a simple (an hopefully correct) be/test.py docstring.W. Trevor King2008-11-136-0/+97
| | |
| * | Created late bug report for Popen OSError catchesW. Trevor King2008-11-133-0/+59
| | |
| * | Catch OSErrors from Popen()sW. Trevor King2008-11-132-7/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From the subprocess module documentation: http://www.python.org/doc/2.5.2/lib/node530.html "The most common exception raised is OSError. This occurs, for example, when trying to execute a non-existent file. Applications should prepare for OSError exceptions." And from the os module documentation: http://www.python.org/doc/2.5.2/lib/module-os.html "exception error This exception is raised when a function returns a system-related error (not for illegal argument types or other incidental errors). This is also known as the built-in exception OSError. The accompanying value is a pair containing the numeric error code from errno and the corresponding string, as would be printed by the C function perror(). See the module errno, which contains names for the error codes defined by the underlying operating system. When exceptions are classes, this exception carries two attributes, errno and strerror. The first holds the value of the C errno variable, and the latter holds the corresponding error message from strerror(). For exceptions that involve a file system path (such as chdir() or unlink()), the exception instance will contain a third attribute, filename, which is the file name passed to the function." I turned this up running be/test.py, when it defaulted to the tla client which I didn't have installed. I don't have things working yet, so I can't create a bug at the moment...
* | | Added ./test_usage.sh as an example usage scenario.W. Trevor King2008-11-161-0/+47
| | | | | | | | | | | | It is also a good integration test.
* | | Removed dud bug 11e. Moved several bugs from 'closed' to 'fixed'.W. Trevor King2008-11-1612-46/+11
| | |
* | | Fix Bug.string() handling of None times.W. Trevor King2008-11-161-3/+7
| | |
* | | Removed the empty bugs 14c and 38b. Fixed bug.string() call in libbe/diff.py.W. Trevor King2008-11-163-57/+1
| | |
* | | Added 'remove' command to remove bugs. Use __desc__ for command help.W. Trevor King2008-11-1621-92/+111
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | Fixed '-' parsing bug for list --assigned option.W. Trevor King2008-11-151-1/+1
| | |
* | | Fixed some errors produced while moving bug_summary to Bug.string().W. Trevor King2008-11-151-15/+17
| | |
* | | Moved libbe.cmdutil.bug_summary() to libbe.bug.Bug.string().W. Trevor King2008-11-157-35/+42
| | | | | | | | | | | | This seems like a natual place for a function that only operates on Bugs.
* | | Removed libbe/template.W. Trevor King2008-11-151-48/+0
| | | | | | | | | | | | | | | This file is not used anywhere, and appears to be an outdated version of libbe/diff.py.
* | | becommands/show.py gives more specific bug information.W. Trevor King2008-11-152-19/+19
| | |
* | | Generalized becommands/list.py to allow more specific bug searches.W. Trevor King2008-11-151-71/+120
| | |
* | | Fixed a few more Comment.date->time calls.W. Trevor King2008-11-142-2/+2
| | | | | | | | | | | | | | | Bug keeps timestamps in Bug.time, so working towards consitency for Comment.
* | | Removerd the diff3 functions from mapfile.py.W. Trevor King2008-11-141-70/+0
| | | | | | | | | | | | They don't seem to be used anywhere...
* | | Fixed some bug.py split effects in diff.pyW. Trevor King2008-11-142-5/+7
| | | | | | | | | | | | | | | | | | Also added 'disabled' status back in so diff doesn't choke trying to load the older versions... Ugly hack, but I don't want to change the past ;).
* | | Split Bug and Comment class out to bug.py from bugdir.pyW. Trevor King2008-11-1417-300/+457
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Comment should probably have it's own file too... I also tried to clean up the interface for setting status and severity. Both attributes involve selecting strings from predefined lists. The lists of valid strings (and descriptions of each string) are now defined in bug.py. The bug.py lists are then used to generate appropriate help strings in becommands/status.py and severity.py. This should make it easier to keep the help strings in synch with the validation information. The original status strings weren't documented, and I didn't know what they all ment, so I elimanted some of them. 'in-progress' and 'disabled' are no longer with us. Of course, it would be simple to add them back in if people don't agree with me on that. Due to the loss of 'disabled' I had to change the status of two bugs (11e and 597) to 'closed'. I removed becommands/inprogress.py as well. It's functionality was replaced by the more general status.py command, which mimics the severity.py command.
* | | Changed __get/setattribute__ calls to get/setattr() calls.W. Trevor King2008-11-141-4/+4
| | | | | | | | | | | | | | | | | | See http://www.python.org/doc/2.5.2/lib/built-in-funcs.html#l2h-33 http://www.python.org/doc/2.5.2/lib/built-in-funcs.html#l2h-66
* | | Replaced libbe.arch.invoke() with general rcs.invoke()W. Trevor King2008-11-141-14/+3
| | |
* | | Added caveat about using short bug names to unique_name().W. Trevor King2008-11-141-0/+4
| | |
* | | Cleaned up and docstringed libbe.cmdutil.unique_name().W. Trevor King2008-11-141-3/+6
| | | | | | | | | | | | | | | Now the first bug will have a 3 char short name (used to be one char, with the second bug having a 3 char name).
* | | Remove blank lines from `be list' outputW. Trevor King2008-11-141-1/+1
| | |
* | | Closed bug 210 (target options not parsed).W. Trevor King2008-11-143-1/+23
| |/ |/| | | | | I imagine this has been fixed for a while...
* | * use python2.4/2.5 compatible import of ElementTreeW. Trevor King2008-11-1316-9/+286
|/ | | | | * catch Popen() calls to missing VCS binaries * test.py should only test installed backends
* Don't require python2.4 for "be".Chris Ball2008-05-161-1/+1
|
* Require editbugs permission to edit bugs. Patch from j@oil21.org.Chris Ball2008-05-161-0/+1
|
*---. Apply patches from j@oil21.org, Ben Finney, Jelmer Vernooij.Chris Ball2008-05-1620-8/+583
|\ \ \
| | | * Makefile: Add with 'clean' target.Ben Finney2008-04-181-0/+27
| | | |
| | * | Fix branding: Bazaar-NG -> Bazaar.Jelmer Vernooij2008-05-141-1/+1
| | | |
| | * | Make setup.py executable.Jelmer Vernooij2008-05-141-0/+0
| | |/
| * / Bugs-Everywhere-Web works with python2.5 do not hardcode python2.4j^2008-04-144-1/+60
| |/
* / Add GIT support, from Chris Ball and Michael Stone.Chris Ball2008-05-163-2/+154
|/
* Assume commit messages are in utf-8 for now...Aaron Bentley2007-07-301-0/+1
|
* Add support for VISUALAaron Bentley2007-07-163-5/+17
|
* Ensure that Arch tests have a user id setAaron Bentley2007-07-162-0/+21
|
* Clarify VISUAL meaningAaron Bentley2007-07-162-0/+30
|