F1rst P0st!!!1!! (and a question)

richard on 2007/03/04 14:59 of Fluffy Menace

Heh. Welcome all to the 4th PyWeek Challenge! This time around I'm fortunate to have joined forces with the talents of fydo and JDruid. Let's see what happens :)

I'm hoping to use pyglet for this challenge, though since it doesn't have sound modules yet we'll still have to use pygame for that bit. The sprite/tile engine in pyglet is still pretty raw but it's there. The window/event stuff is pretty good though, and I'll be using PyOpenGL a fair bit too. I guess the biggest issue I have is that pyglet isn't released and isn't going to be for a long time. That means it really shouldn't be used for pyweek. So I thought I'd ask here for some opinions. What do you think? Should I be allowed to use pyglet for this challenge?

(log in to comment)

Comments

Adam on 2007/03/04 15:50:

Hmm, I don't really think you should be able to use this unless you make it available in some way and with some sort of documentation as well so others can use it. Why do you say it isn't going to be released for a long time?

Adam on 2007/03/04 15:56:

I just looked at the site some more and I see that you can get it via svn so if there is at least a decent amount of commenting I don't see any problem with using it as long as it's clear that people can get the code. If you click on the 'get involved' button from the main pyglet page svn instructions are there.

RB[0] on 2007/03/04 20:14:

if it has docs and others can get it, as the rules state, I think its ok :)

RB[0] on 2007/03/04 20:44:

I just looked at the site, and it says that it doesnt yet have any docs.
Is that the case, or am I missing something?

Last time around I remember you telling me that "There really needs to be a plain-English overview description of what the library does, what its components are, what their API is, how they're intended to be used, etc."

If this lib has these I'd say its okay

fydo on 2007/03/06 01:16:

I might be a little biased, but I think that Richard should be able to use pyglet, provided that he provides an archive or snapshot of the SVN as a downloadable archive. (perhaps even privately just on pyweek.org)

That way, if one of the other pyglet maintainers makes a change to the SVN, it won't affect those who are using the library in Pyweek. i.e. they won't be working against a 'moving target' API.

richard on 2007/03/06 03:49:

I'm going to be in transit back from the US in about 12 hours (for about 30 hours) but I hope to try to do some pyglet work once I'm back. There will be a particular focus on the API and docs.

There is still a chance that the sprite engine in pyglet won't be ready. The image/text/window/event stuff will be though, so a snapshot is entirely reasonable.

richard on 2007/03/09 08:14:

I've decided that using pyglet really wouldn't be fair on the other people entering the challenge.

I may still use it (and disqualify my team's entry from the rankings) but I'd have to discuss that with my team first.

Treeform on 2007/03/09 19:01:

i have a lib nice 3d lib mygl ... but it has no nice documination so i decided not to use it for this challenge, it would be unfair if you could use yours.

saluk on 2007/03/09 21:38:

I'd really like to see what pyglet can do. Haven't gotten any of the demos to run on either my windows or linux computer, but haven't tried very hard either.

By the way, I think comments should link back to the commenters profile or something.

simonwittber on 2007/03/11 10:40:

IMO, Pyglet should definitely be OK for use in Pyweek. I don't think the question even needed asking :-)

Everyone knows where it is, if anyone wants to use it, there are plenty of tests (tests are the best kind of documentation). The fact that the code is in SVN is not a barrier to use for anyone with half a clue.

I also think that in the context of this challenge, Pyglet doesn't provide any real advantages over someone elses random combination of Pygame/PyOpenGL/Whatever.

RB[0] on 2007/03/11 15:04:

Yes, but in the past Richard has required a pure english document explaining every aspect of the lib, it classes/functions how they are to be used and what they return.

Not to mention the new rule that explicitly explains a lib must be released, not just available,with documentation 1 month prior to the compo.

Plus, Richard has already stated that it would be unfair if he used pyglet, and he would disqualify himself if he used it, and he must have had a reason for saying this.