View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000500 | ascend | build-windows | public | 2011-03-25 14:04 | 2011-03-28 11:49 |
| Reporter | john | ||||
| Assigned To | john | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Platform | Windows | OS | Windows | OS Version | 7 |
| Product Version | 0.9.7 | ||||
| Target Version | 0.9.8 | Fixed in Version | 0.9.8 | ||
| Summary | 0000500: script 'pygtk/ascdev' infinite-looping on Windows 7 | ||||
| Description | Something is going wrong in the processing of environment variables in the 'pygtk/ascdev' script on Windows 7. It seems that the same element is repeatedly being added to the path string, possibly due to some bug in the list processing code of the 'add_at_start' function in that script. | ||||
| Tags | No tags attached. | ||||
|
|
This problem appears as a result of PATH manipulations being done by the PyGTK All-In-One component for Python. Somehow, it is causing the location of the GTK runtime to be added at the start of the PATH, which confounds the 'add_at_start' code's attempt to get the ordering correct. One solution would be not to remove items, only to add them if missing. Assume that the user knows best with regard to setting this up (it's a dev script after all!) |
|
|
Fixed by changing the function to NOT remove locations already present in PATH. Only add those that are missing, by adding them at the start. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2011-03-25 14:04 | john | New Issue | |
| 2011-03-25 14:04 | john | Status | new => assigned |
| 2011-03-25 14:04 | john | Assigned To | => john |
| 2011-03-26 11:22 | john | Note Added: 0000697 | |
| 2011-03-28 11:49 | john | Note Added: 0000698 | |
| 2011-03-28 11:49 | john | Status | assigned => resolved |
| 2011-03-28 11:49 | john | Fixed in Version | => 0.9.8 |
| 2011-03-28 11:49 | john | Resolution | open => fixed |
