Modify ↓
#283 closed defect (duplicate)
python:exec can not change to the build dir correctly
Reported by: | xieyanbo@… | Owned by: | cmlenz |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | Build slave | Version: | dev |
Keywords: | Cc: | ||
Operating System: | Linux |
Description
When output file be specified, python:exec will not change current work directory to the build dir correctly, that makes pylint report something like this: no module named xxx.
My Bitten: 0.6dev-r545
Patch attached.
Attachments (1)
Change History (3)
Changed 17 years ago by xieyanbo@…
comment:1 Changed 16 years ago by flavour@…
comment:2 Changed 15 years ago by osimons
- Milestone 0.6 deleted
- Resolution set to duplicate
- Status changed from new to closed
As python:exec calls sh:execute internally, it sure looks highly likely that they are duplicates. I'll go for that and closing this one as a duplicate of #233.
Note: See
TracTickets for help on using
tickets.
I get the same error with Windows XP & Bitten: 0.6dev_r567 Python: 2.5.4 Lint runs fine from Python, but fails from Bitten: Cannot execute Python module pylint.lint: No module named pylint.lint pylint.lint doesn't exist on my working Linux system either
This seems to be a duplicate of #233 The same patch is attached to both, but it seems to have already been applied to Trunk, so can't be used to solve my issue...