Re: [Scons-dev] User Guide generation questions

2014-08-31 Thread William Blevins
That may be a valid problem though because when I run *scons* from #
*doc/user* the index.html generated from the build is completely empty.

V/R,
William


On Fri, Aug 29, 2014 at 6:44 PM, Dirk Bächle tshor...@gmx.de wrote:

  On 30.08.2014 00:12, William Blevins wrote:

 I am trying to make some misc updates to the User Guide, and I am having
 some issues. I thought it might be a problem with a document do I tried
 docs-validate and there were two errors:

  [...]


   81.11% (176/217) doc/user/scons_ex.xml
 ERROR: doc/user/scons_ex.xml fails to validate:
 Element 'programlisting': This element is not expected. Expected is one
 of ( {http://www.scons.org/dbxsd/v1.0}refentry.class, {
 http://www.scons.org/dbxsd/v1.0}refentry, {
 http://www.scons.org/dbxsd/v1.0}section.class, {
 http://www.scons.org/dbxsd/v1.0}section, {
 http://www.scons.org/dbxsd/v1.0}toc, {http://www.scons.org/dbxsd/v1.0}lot,
 {http://www.scons.org/dbxsd/v1.0}index, {
 http://www.scons.org/dbxsd/v1.0}glossary, {
 http://www.scons.org/dbxsd/v1.0}bibliography, {
 http://www.scons.org/dbxsd/v1.0}simplesect )., line 4116
 81.57% (177/217) doc/user/sconf.xml
 [...]


   92.63% (201/217) doc/user/scons_exi.xml
 ERROR: doc/user/scons_exi.xml fails to validate:
 Element 'programlisting': This element is not expected. Expected is one
 of ( {http://www.scons.org/dbxsd/v1.0}refentry.class, {
 http://www.scons.org/dbxsd/v1.0}refentry, {
 http://www.scons.org/dbxsd/v1.0}section.class, {
 http://www.scons.org/dbxsd/v1.0}section, {
 http://www.scons.org/dbxsd/v1.0}toc, {http://www.scons.org/dbxsd/v1.0}lot,
 {http://www.scons.org/dbxsd/v1.0}index, {
 http://www.scons.org/dbxsd/v1.0}glossary, {
 http://www.scons.org/dbxsd/v1.0}bibliography, {
 http://www.scons.org/dbxsd/v1.0}simplesect )., line 4367
 Validation failed! Please correct the errors above and try again.


  Can I remove those sections? I'm not that familiar with the schema.

   The failing files scons_ex.xml and scons_exi.xml are generated
 during the actual build process. Remove them by hand, or do a scons -c
 before trying to validate...

 Regards,

 Dirk


 ___
 Scons-dev mailing list
 Scons-dev@scons.org
 http://two.pairlist.net/mailman/listinfo/scons-dev


___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev


Re: [Scons-dev] User Guide generation questions

2014-08-31 Thread Mark Flacy
Do you have a branch/repo I can pull from/clone to see?

I use docbook a lot.

On August 31, 2014 10:51:14 AM CDT, William Blevins wblevins...@gmail.com 
wrote:
That may be a valid problem though because when I run *scons* from #
*doc/user* the index.html generated from the build is completely empty.

V/R,
William


On Fri, Aug 29, 2014 at 6:44 PM, Dirk Bächle tshor...@gmx.de wrote:

  On 30.08.2014 00:12, William Blevins wrote:

 I am trying to make some misc updates to the User Guide, and I am
having
 some issues. I thought it might be a problem with a document do I
tried
 docs-validate and there were two errors:

  [...]


   81.11% (176/217) doc/user/scons_ex.xml
 ERROR: doc/user/scons_ex.xml fails to validate:
 Element 'programlisting': This element is not expected. Expected is
one
 of ( {http://www.scons.org/dbxsd/v1.0}refentry.class, {
 http://www.scons.org/dbxsd/v1.0}refentry, {
 http://www.scons.org/dbxsd/v1.0}section.class, {
 http://www.scons.org/dbxsd/v1.0}section, {
 http://www.scons.org/dbxsd/v1.0}toc,
{http://www.scons.org/dbxsd/v1.0}lot,
 {http://www.scons.org/dbxsd/v1.0}index, {
 http://www.scons.org/dbxsd/v1.0}glossary, {
 http://www.scons.org/dbxsd/v1.0}bibliography, {
 http://www.scons.org/dbxsd/v1.0}simplesect )., line 4116
 81.57% (177/217) doc/user/sconf.xml
 [...]


   92.63% (201/217) doc/user/scons_exi.xml
 ERROR: doc/user/scons_exi.xml fails to validate:
 Element 'programlisting': This element is not expected. Expected is
one
 of ( {http://www.scons.org/dbxsd/v1.0}refentry.class, {
 http://www.scons.org/dbxsd/v1.0}refentry, {
 http://www.scons.org/dbxsd/v1.0}section.class, {
 http://www.scons.org/dbxsd/v1.0}section, {
 http://www.scons.org/dbxsd/v1.0}toc,
{http://www.scons.org/dbxsd/v1.0}lot,
 {http://www.scons.org/dbxsd/v1.0}index, {
 http://www.scons.org/dbxsd/v1.0}glossary, {
 http://www.scons.org/dbxsd/v1.0}bibliography, {
 http://www.scons.org/dbxsd/v1.0}simplesect )., line 4367
 Validation failed! Please correct the errors above and try again.


  Can I remove those sections? I'm not that familiar with the schema.

   The failing files scons_ex.xml and scons_exi.xml are generated
 during the actual build process. Remove them by hand, or do a scons
-c
 before trying to validate...

 Regards,

 Dirk


 ___
 Scons-dev mailing list
 Scons-dev@scons.org
 http://two.pairlist.net/mailman/listinfo/scons-dev






___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev


Re: [Scons-dev] Re PR #171

2014-08-31 Thread Gary Oberbrunner
On Sun, Aug 31, 2014 at 1:42 PM, Russel Winder rus...@winder.org.uk wrote:

 The whole ASCII string / Unicode codepoint sequence thing brings the
 Python 2/Python 3 thing to a head. If we want a codebase that runs under
 both Python 2 and Python 3 then we almost certainly have to use six to
 provide the indirection layer for things like strings (unless we write
 our own). Alternatively the Python 3 codebase can be separate (which is
 what Anatoly was advocating if I remember correctly) and then do careful
 cherry picks from the Python 2 codebase.


six.py is now included in the python3 branch.  At this point not everything
works (still a long way from it) but I see no showstopping issues that have
cropped up yet.  (By showstopping I mean something that would prevent
shipping a single codebase that works in 2.7 and 3.x.)



 There is also then process: I can probably spend an hour here an hour
 there fixing broke tests but should these individual sessions be
 separate pull requests?


Sure.  On the python3 branch.  If you have a bunch of related ones, I see
no reason those couldn't be reviewed and merged together.

-- 
Gary
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev


[Scons-dev] Quick Sanity Check

2014-08-31 Thread Russel Winder
Has anyone claimed that the python3 branch has ever compiled with Python
3?

There are some obvious errors in my checkout that mean the code base can
never have actually compiled.

If my checkout is the real python3 branch, I will hit the obvious low
hanging fruit.

-- 
Russel.
=
Dr Russel Winder  t: +44 20 7585 2200   voip: sip:russel.win...@ekiga.net
41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev


Re: [Scons-dev] User Guide generation questions

2014-08-31 Thread Dirk Bächle

William,

On 31.08.2014 19:50, William Blevins wrote:
This is happening from a clean scons checkout with no local changes. 
 I am currently at revision 3187:605ae0a39155.  I assume this is also 
an issue in default latest.


Using python 2.6 on a RHEL6 or equivalent linux distro.

I'm currently at revision 3189:98dea26fbc96 and I can build the docs 
just fine. My working directory is #doc/user and I call


  python ../../src/script/scons.py

. Please ensure that you have the following Python bindings on your 
system libxml2+libxslt or lxml.


Regards,

Dirk


V/R,
William


On Sun, Aug 31, 2014 at 12:56 PM, Mark Flacy mfl...@verizon.net 
mailto:mfl...@verizon.net wrote:


Do you have a branch/repo I can pull from/clone to see?

I use docbook a lot.


On August 31, 2014 10:51:14 AM CDT, William Blevins
wblevins...@gmail.com mailto:wblevins...@gmail.com wrote:

That may be a valid problem though because when I run
*scons* from #*doc/user* the index.html generated from the
build is completely empty.

V/R,
William



___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev


Re: [Scons-dev] User Guide generation questions

2014-08-31 Thread William Blevins

 python ../../src/script/scons.py
 Please ensure that you have the following Python bindings on your system
 libxml2+libxslt or lxml.


I have *python-lxml-2.2.3-1* installed.

I tried *python ../../src/script/scons.py* with both python 2.6 and python
2.7 with the same results (from what I could tell).  There is an index.html
in *#doc/user* that has been committed but it doesn't seem to update, and
the index.html inside *#doc/user/scons-user* is empty (size 0 bytes).

I was able to generate these files correctly (I assume) when I updated docs
for Issue2395, but my baseline was probably from a month ago or longer.

V/R,
William


On Sun, Aug 31, 2014 at 3:08 PM, Dirk Bächle tshor...@gmx.de wrote:

  William,


 On 31.08.2014 19:50, William Blevins wrote:

 This is happening from a clean scons checkout with no local changes.  I am
 currently at revision 3187:605ae0a39155.  I assume this is also an issue in
 default latest.

  Using python 2.6 on a RHEL6 or equivalent linux distro.

   I'm currently at revision 3189:98dea26fbc96 and I can build the docs
 just fine. My working directory is #doc/user and I call

   python ../../src/script/scons.py

 . Please ensure that you have the following Python bindings on your system
 libxml2+libxslt or lxml.

 Regards,

 Dirk


  V/R,
 William


 On Sun, Aug 31, 2014 at 12:56 PM, Mark Flacy mfl...@verizon.net wrote:

 Do you have a branch/repo I can pull from/clone to see?

 I use docbook a lot.


 On August 31, 2014 10:51:14 AM CDT, William Blevins 
 wblevins...@gmail.com wrote:

 That may be a valid problem though because when I run *scons* from #
 *doc/user* the index.html generated from the build is completely empty.

  V/R,
 William



 ___
 Scons-dev mailing list
 Scons-dev@scons.org
 http://two.pairlist.net/mailman/listinfo/scons-dev


___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev


Re: [Scons-dev] Quick Sanity Check

2014-08-31 Thread Gary Oberbrunner
That branch is the one.  If you check the commits on that branch you'll see
who's been committing to it.  I just yesterday got a python3 installed, so
I haven't touched it under python3, though I have kept pushing it back into
functioning on python2 (but not all the way there yet either).  So yeah,
there is plenty of juicy low-hanging fruit. :-)


On Sun, Aug 31, 2014 at 5:34 PM, Bill Deegan b...@baddogconsulting.com
wrote:

 Russel,

 I'm hoping to get a python3 buildbot slave up and running against the
 python3 branch sometime this week.
 That way it will be easier to keep an eye on it's current status.

 -Bill


 On Sun, Aug 31, 2014 at 11:37 AM, Russel Winder rus...@winder.org.uk
 wrote:

 Has anyone claimed that the python3 branch has ever compiled with Python
 3?

 There are some obvious errors in my checkout that mean the code base can
 never have actually compiled.

 If my checkout is the real python3 branch, I will hit the obvious low
 hanging fruit.

 --
 Russel.

 =
 Dr Russel Winder  t: +44 20 7585 2200   voip:
 sip:russel.win...@ekiga.net
 41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
 London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

 ___
 Scons-dev mailing list
 Scons-dev@scons.org
 http://two.pairlist.net/mailman/listinfo/scons-dev



 ___
 Scons-dev mailing list
 Scons-dev@scons.org
 http://two.pairlist.net/mailman/listinfo/scons-dev




-- 
Gary
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev