Can I use old me pyweek's game lib ?

I haven't time to write more. so I want to use my old game lib in pyweek.
Can I use it ?

(log in to comment)

Comments

This seems like something of a grey area. Technically the answer is no, you can't use personal codebases. But old pyweek games are already 'released' by definition, though I guess not as libraries per se. 
From the rules:

"You are not allowed to use any exising personal codebases. This includes using those codebases as a point of reference. Hint: release the code well before the comp as part of a tutorial. Then you may refer to it -- and so may the other competitors."
Hey Richard - but it it's part of a previous pyweek entry, then surely it is released, and has been clearly visible to other pyweek entrants for a long time? I'm not unhappy if you think that's not in the spirit, but seeking to clarify. Thanks for your ideas on this.
It might have been part of a game but if it's not documented as a library in some way it's not really accessible to others. It's really just a point of fairness in my view.
If I use the old pyweek's game lib Concepts, and rewrite the base code ?!
If I use the old pyweek's game lib Concepts, and rewrite the base code ?!
Fair enough Richard, that seems reasonable. Thanks for making a call.

Milker: I think the above discussion implies that code from old PyWeek games is generally not allowed, unless you already announced to PyWeek participants a public release of the 'lib' portion of it as a well-documented library that others would be able to easily download and use.
Hmmm, what about using code from other people's Pyweek entries? I wasn't planning to do that per se, but maybe I was gonna steal some artwork and/or music.
@Cosmo it's a tough one because there's a number of us who are likely to want to use the modified squirtle that's found in my game from last PyWeek. I'm pretty comfortable with that because the API is pretty much as it is for standard squirtle (and thus well-documented) with a small (again, documented) extension to handle layers. So I see that as OK.

I really should have made an actual release of my squirtle fork though. Bad Richard.

It's a fuzzy line - it always has been - but the way I see it is if the code's opaque and not accessible to others then it's not really fair to use it.
I agree with Cosmo - why don't you use a Pyweek that somebody else wrote, then you won't gain an unfair advantage?