A | B | C | D | E | F | G | |
---|---|---|---|---|---|---|---|
1 | ID | Votes | Type/Member | Milestone | Pri | Owner | Summary/Comments |
2 | |||||||
3 | 2427 | 0 | DEFECT | triage | P4 | issues@scons | STATIC_AND_SHARED_OBJECTS_ARE_THE_SAME not in man page |
4 | almost consensus from last time: document it, but forgot milestone, priority, owner | ||||||
5 | |||||||
6 | Bill | doc+anytime | p3 | Bill | Agree with Steven | ||
7 | Brandon | ||||||
8 | David | ||||||
9 | Gary | doc | Either need this or a supported way to set the "shared" attribute on an obj, and in most cases this hack is easier to use. | ||||
10 | Greg | invalid | This is an internal hack that shouldn't be exposed. @Steven, I'd have an Ar() or Archive() builder that took any kind of object and could be used for the kinds of things they're trying to do. Don't forget, the original purpose of the `ar` command was to build archives; the use for libraries came later. | ||||
11 | Jim | ||||||
12 | Ken | ||||||
13 | Sohail | ||||||
14 | Jim | ||||||
15 | Ken | ||||||
16 | Sohail | ||||||
17 | Steven | ? | I don't view it as an internal hack. If we don't document this, then what mechanism would you suggest for controlling this behavior? It's downright necessary to make certain configurations work with Visual C++. | ||||
18 | |||||||
19 | 2443 | 0 | DEFECT | triage | P4 | issues@scons | Aliases with actions are broken |
20 | consensus | ||||||
21 | |||||||
22 | Bill | research | Bill | ||||
23 | Brandon | ||||||
24 | David | ||||||
25 | Gary | p2 | agree w/ Greg; Actions on Aliases are supposed to work. This line looks really suspicious: result = env.subst_list(self.cmd_list, 0, executor=executor) since scons_subst_list doesn't take an executor kw arg. | ||||
26 | Greg | see note | I can confirm that it fails as he says. Actions on Alias() are documented, so this is a regression and high priority, but who has time to work on it? | ||||
27 | Jim | ||||||
28 | Ken | ||||||
29 | Sohail | ||||||
30 | Steven | DEFER | too much discussion, next time | ||||
31 | |||||||
32 | 2444 | 0 | DEFECT | triage | P4 | issues@scons | Unclear where env.WhereIs searches for executables |
33 | consensus | ||||||
34 | |||||||
35 | Bill | doc | Bill | ||||
36 | Brandon | ||||||
37 | David | ||||||
38 | Gary | doc | +Easy | ||||
39 | Greg | +Easy | Ah, English, ain't it grand? It ought to be a trivial change, so who can take it? | ||||
40 | Jim | ||||||
41 | Ken | ||||||
42 | Sohail | ||||||
43 | Steven | ||||||
44 | |||||||
45 | 2445 | 0 | DEFECT | triage | P4 | issues@scons | Scons is not works with Python 3.1 |
46 | almost consensus: invalid, but discuss PYTHON RANGE and CHANGE REQUIREMENT NOW | ||||||
47 | |||||||
48 | Bill | invalid + 1.3 | p1 | bill | Agree with Greg. Do we need to create a bug to track checking the python version to be in the supported range, rather than just > some value? [ add logic to check python verison in current range] | ||
49 | Brandon | ||||||
50 | David | ||||||
51 | Gary | invalid | agreed. | ||||
52 | Greg | invalid | I'm not sure of all the places where we claim compatibility back to 1.5.2, but we should start tracking them down and making them "2.2 but not 3.x." | ||||
53 | Jim | ||||||
54 | Ken | ||||||
55 | Sohail | ||||||
56 | Steven | ||||||
57 | |||||||
58 | 2446 | 0 | DEFECT | triage | P4 | issues@scons | Variables instance bug |
59 | consensus | ||||||
60 | |||||||
61 | Bill | ||||||
62 | Brandon | ||||||
63 | David | ||||||
64 | Gary | Greg: assume you mean 2450. (((Yes, I corrected it; dyslexics of the world, untie!))) | |||||
65 | Greg | included in 2450 below | I have to admit I don't know what the code is supposed to be doing, but Steven wrote it, so I'll defer to him. Variables.instance isn't used anywhere else as far as I can find, so the code doesn't seem to have any effect. See also 2450 below, which removes this line as a side-effect. | ||||
66 | Jim | ||||||
67 | Ken | ||||||
68 | Sohail | ||||||
69 | Steven | ||||||
70 | |||||||
71 | 2447 | 0 | DEFECT | triage | P4 | issues@scons | Uknown variables incorrect when updating multiple times. |
72 | consensus | ||||||
73 | |||||||
74 | Bill | ||||||
75 | Brandon | ||||||
76 | David | ||||||
77 | Gary | I think this usage should be permitted, so I would *not* mark invalid. I asked him for a patch. | |||||
78 | Greg | invalid or dup 2450 | The man page doesn't say either way whether Update is a one-time thing. I don't use Variables(), so I can't tell how common or useful this kind of thing might be. I'm inclined to mark this INVALID and change the doc to match the code. See also 2450 below. | ||||
79 | Jim | ||||||
80 | Ken | ||||||
81 | Sohail | ||||||
82 | Steven | ||||||
83 | |||||||
84 | 2448 | 0 | ENHANCEMENT | triage | P4 | issues@scons | Need to be able to profile just script execution or just depenency walk |
85 | consensus | ||||||
86 | |||||||
87 | Bill | 2.x | p3 | Sounds useful to me. I've had some larger build systems and just profiling the non scons code would be useful. Though it might be non-trivial when it comes to running user created scanners and emitters? | |||
88 | Brandon | ||||||
89 | David | ||||||
90 | Gary | 3.x | p4 | Ken or 3.x | Would be nice, no time for it in the near term unless he'd like to contribute. | ||
91 | Greg | Ken? | Ken makes a good point and this is something I wouldn't mind having around when testing TaskmasterNG, but I can't see spending any core developer time on it, either. Maybe Ken has a patch? | ||||
92 | Jim | ||||||
93 | Ken | ||||||
94 | Sohail | ||||||
95 | Steven | ||||||
96 | |||||||
97 | 2449 | 0 | DEFECT | triage | P4 | issues@scons | Race condition when using -j on Windows (workaround included) |
98 | consensus | ||||||
99 | |||||||
100 | Bill | 2.x | p1 | Can we bump 2.0's python version to 2.4? If so then lets go subprocess. An I sugguest we do go to at least 2.4. But that's a larger discussion. |