You may just need to import the constants from python modules to be available..?
On Tue, Nov 18, 2014 at 4:08 PM, Shreedhar Manek <shreedharma...@gmail.com> wrote: > From the description - > > The Chmod action requires a numeric for the mode. For a long time now the > chmod command has processed string modes so the user does not have to > remember or look > up the numeric values. The Chmod action should allow forthe string mode > specification. > > The Chmod action referred to here is the os.chmod() method in the source > code, correct? So consequently what I need to do is convert a string to its > corresponding octal integer so that the Chmod action can accept the string > too. Can you confirm? > > Thanks. > > On Tue, Nov 18, 2014 at 1:59 PM, Dirk Bächle <tshor...@gmx.de> wrote: > >> Shreedhar, >> >> On 18.11.2014 07:29, Shreedhar Manek wrote: >> >>> Hi, >>> I had emailed on here a few days back asking for some help so that I can >>> contribute to SCons. I'm grateful for the response and I read the guides >>> that I was directed to. >>> >>> I read up to chapter 8 of the documentation beyond which it was getting >>> a tad bit complicated for me. I shall absolutely get back to it later >>> (college end semester exams coming up!). I also looked around on the other >>> links (man page, developer's guide). >>> >>> I checked the bug marked 'easy' on tigris and I found this one which I'd >>> like to fix - http://scons.tigris.org/issues/show_bug.cgi?id=2494. >>> Unfortunately, I have absolutely no idea what I should do next to go about >>> fixing the same. What do I do next? >>> >>> the next steps for you would be: >> >> - ensuring that you can run your forked version of the repo (see >> README.rst in top-level folder) >> - running a full regression test with "python runtest.py -a" >> - finding the "Chmod" method in the sources >> - ensuring that it's the right place you've found, for example by >> adding a simple print statement to it >> - changing the "Chmod" to show the wanted behaviour >> - running the regression test again, to ensure that you didn't break >> anything >> - adapting/adding tests and documentation for the new/changed >> functionality >> - create your pull request >> >> or something along those lines. >> >> >> Best regards, >> >> Dirk >> >> >> _______________________________________________ >> Scons-dev mailing list >> Scons-dev@scons.org >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> > > > _______________________________________________ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > >
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev