Merge lp:~jelmer/bzr/direct-cstringio-import into lp:bzr/2.3
Proposed by
Jelmer Vernooij
Status: | Merged |
---|---|
Approved by: | Martin Packman |
Approved revision: | no longer in the source branch. |
Merged at revision: | 5665 |
Proposed branch: | lp:~jelmer/bzr/direct-cstringio-import |
Merge into: | lp:bzr/2.3 |
Diff against target: |
32 lines (+4/-1) 2 files modified
bzrlib/config.py (+1/-1) doc/en/release-notes/bzr-2.3.txt (+3/-0) |
To merge this branch: | bzr merge lp:~jelmer/bzr/direct-cstringio-import |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Martin Packman (community) | Approve | ||
Review via email: mp+86221@code.launchpad.net |
This proposal supersedes a proposal from 2011-12-18.
Commit message
Directly import cStringIO in bzrlib.config to prevent lazy import scope errors.
Description of the change
Directly import cStringIO in bzrlib.config, rather than through
lazy_import. This fixes a IllegalUseOfSco
running into.
We use cStringIO heavily, so - like e.g. the os module - it seems impossible
to avoid it anyway.
(resubmitted against 2.3)
To post a comment you must log in.
Yeah, this is the change I was thinking of, but would retarget to 2.3 as it's safe and that's the version being used by the reporter. For trunk, we want the full fix of changing lazy imports to be less thread-ignorant, as in:
<https:/ /code.launchpad .net/~gagern/ bzr/bug396819- lazy_import- threadsafe/ +merge/ 73475>