Issue #140 wontfix

comma in path name conflicts with coverage glob expansion

Zooko O'Whielacronx
created an issue

I just encountered this problem:

{{{ HACK zompu:~/playground/tahoe-lafs/ticket999-support_multiple_storage_backends,_including_amazon_s3-joshes_new_work$ PYTHONPATH=src:support/lib/python2.6/site-packages /usr/local/bin/coverage run --branch --include="pwd/src/*" /usr/local/bin/trial allmydata.test.test_backends allmydata.test.test_backends TestBackendConstruction test_create_fs_backend ... [OK] TestServerConstruction test_create_server_fs_backend ... [OK] TestServerFSBackend test_out_of_space ... [OK] test_read_share ... [OK] test_write_share ... [OK] TestServerNullBackend test_write_share ... [OK]


Ran 6 tests in 0.541s

PASSED (successes=6) Coverage.py warning: No data was collected.

HACK zompu:~/playground/tahoe-lafs/ticket999-support_multiple_storage_backends,_including_amazon_s3-joshes_new_work$ cd .. HACK zompu:~/playground/tahoe-lafs$ mv ticket999-support_multiple_storage_backends,_including_amazon_s3-joshes_new_work ticket999-support_multiple_storage_backends_including_amazon_s3-joshes_new_work/ HACK zompu:~/playground/tahoe-lafs$ cd !$ cd ticket999-support_multiple_storage_backends_including_amazon_s3-joshes_new_work/ HACK zompu:~/playground/tahoe-lafs/ticket999-support_multiple_storage_backends_including_amazon_s3-joshes_new_work$ PYTHONPATH=src:support/lib/python2.6/site-packages /usr/local/bin/coverage run --branch --include="pwd/src/*" /usr/local/bin/trial allmydata.test.test_backends allmydata.test.test_backends TestBackendConstruction test_create_fs_backend ... [OK] TestServerConstruction test_create_server_fs_backend ... [OK] TestServerFSBackend test_out_of_space ... [OK] test_read_share ... [OK] test_write_share ... [OK] TestServerNullBackend test_write_share ... [OK]


Ran 6 tests in 0.691s

PASSED (successes=6) }}}

I don't know if or how coverage should be changed to make this not happen to people who have commas in their path names. :-(

Comments (1)

  1. Ned Batchelder repo owner

    It looks to me like you should either use a relative file name in your --include option, or use a .coveragerc file. I don't see a good way to make this possible with the command-line.

  2. Log in to comment