It's taking me longer than expected to finish building the
distribution packages.
There are instructions in doc/internal/dist.txt describing how to put
together the release, I'm having problems with generating the
documentation.
My environment throws a traceback with some interaction between
docutils and epydoc when generating the html api reference. Last
couple of lines of the traceback:
File "/usr/local/lib/python2.6/dist-packages/docutils-0.6-py2.6.egg/
docutils/nodes.py", line 129, in walk
visitor.dispatch_visit(self)
File "/usr/local/lib/python2.6/dist-packages/docutils-0.6-py2.6.egg/
docutils/nodes.py", line 1604, in dispatch_visit
return method(node)
File "/home/ben/pygletdev/pyglet-1.1.4-rc1/tools/epydoc/epydoc/
markup/restructuredtext.py", line 305, in visit_paragraph
m = re.match(r'(\s*[\w\W]*?\.)(\s|$)', child.data)
AttributeError: 'Text' object has no attribute 'data'
This may or may not be causing a second error when generating the html
guide:
Generating HTML guide...
Traceback (most recent call last):
File "tools/gendoc_html.py", line 388, in <module>
api_objects = get_api_objects(options.apidoc_dir)
File "tools/gendoc_html.py", line 360, in get_api_objects
apidoc_file = open(os.path.join(apidoc_dir, 'api-objects.txt'))
IOError: [Errno 2] No such file or directory: 'tools/../doc/html/api/
api-objects.txt'
And yeah, that file doesn't exist, though the directory does. I
suspect it's put there by the preceding stage.
The final error I'm seeing I'm also having a hard time tracking down,
I get an ImportError from the line "from docutils.writers import
docbook" and I so far haven't discovered the package that supplies
this.
I'm afraid I'm fairly unfamiliar with these tools, so it could be as
simple as a misconfiguration.
I've been able to put together the .msi package, source package, and
the various eggs and spending some time here and there on these
problems.
-b
On Oct 9, 11:14 am, Ben Smith <[email protected]> wrote:
> Howdy - I'm considering throwing together a release candidate in the
> next week or so, unless I get a reason not to.
>
> -b
>
> On Oct 7, 9:36 pm, Paweł Sobkowiak <[email protected]> wrote:
>
>
>
> > I browsed through SVN logs and it seems that backports were completed
> > at the end of August.
>
> > When will 1.1.4 be released?
>
> > On Sep 10, 8:44 pm, claudio canepa <[email protected]> wrote:
>
> > > On Thu, Sep 10, 2009 at 12:56 PM, Ben Smith
> > > <[email protected]>wrote:
>
> > > > Hello,
>
> > > > With pyweek over, I'd like to do what I can to make a pyglet 1.1.4
> > > > maintenance release from all the trunk backports done before pyweek.
> > > > I'm just testing the waters here, is anyone else interested in a new
> > > > maintenance release? If so, which (if any) open issues should be
> > > > addressed? How has the release process typically worked, and what can
> > > > I do to help it along?
>
> > > > Thanks,
> > > > -b
>
> > > I think it is a good idea: the current release will crash in at least two
> > > situations, those are fixed in maintenance.
> > > And, it would be good that the recent bugfixes get tested in the wild,
> > > which
> > > only would happen if released.
> > > While anyone can be tempted to say 'wait, let fix this or that', I would
> > > say
> > > 'lets offer a better pyglet now, there always be time to do another
> > > release'.
>
> > > The only tempting additions atm are:
> > > Two linux issues, with patches: 452 , 387
>
> > > but maybe linux people can chime in about how good looking are the
> > > patches ?
>
> > > --
> > > claudio
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pyglet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
