| 2012-06-19 20:28:01 |
James Westby |
bug |
|
|
added bug |
| 2012-06-19 20:29:00 |
James Westby |
description |
oops.Config.publishers was deprecated in favour of oops.Config.publisher and
oops.publishers.PublishToMany. The old codepath should be removed once
sufficient time has elapsed to allow users to migrate.
I expect most users will be internal to Canonical, so checking the CAT repo
for things that depend on python-oops-* and auditing them would be one
way to check.
Thanks,
James |
oops.Config.publishers was deprecated in favour of oops.Config.publisher and
oops.publishers.PublishToMany. The old codepath should be removed once
sufficient time has elapsed to allow users to migrate.
I expect most users will be internal to Canonical, so checking the CAT repo
for things that depend on python-oops-* and auditing them would be one
way to be sure that nothing would break.
Thanks,
James |
|
| 2017-09-04 10:05:34 |
Colin Watson |
bug task added |
|
python-oops-twisted |
|
| 2017-09-04 10:05:41 |
Colin Watson |
python-oops-twisted: status |
New |
Triaged |
|
| 2017-09-04 10:05:44 |
Colin Watson |
python-oops-twisted: importance |
Undecided |
Low |
|
| 2017-09-04 10:06:51 |
Colin Watson |
description |
oops.Config.publishers was deprecated in favour of oops.Config.publisher and
oops.publishers.PublishToMany. The old codepath should be removed once
sufficient time has elapsed to allow users to migrate.
I expect most users will be internal to Canonical, so checking the CAT repo
for things that depend on python-oops-* and auditing them would be one
way to be sure that nothing would break.
Thanks,
James |
oops.Config.publishers was deprecated in favour of oops.Config.publisher and
oops.publishers.publish_to_many. The old codepath should be removed once
sufficient time has elapsed to allow users to migrate.
I expect most users will be internal to Canonical, so checking the CAT repo
for things that depend on python-oops-* and auditing them would be one
way to be sure that nothing would break.
Thanks,
James |
|
