On Sat, Feb 21, 2009 at 2:54 PM, Andrew Godwin <and...@aeracode.org> wrote:

>
> Hello everyone,
>
> I'm currently working on the next version of South
> [http://south.aeracode.org], and I need some test fodder for our new
> models.py parser - rather than our previous approach using regexes and a
> reasonable amount of hope, this time it's being done properly, using the
> python parsing modules.
>
> (There are reasons we have to parse the file directly rather than
> introspecting from the model objects at runtime, mostly to do with
> custom fields. If you'd me like to elaborate, or prove me wrong, please
> feel free to start a debate.)
>
> Still, while I have my own set of Django apps to test it on, I'm in sore
> need of a decent load of edge cases, and other testing material. Thus,
> if you have an example models.py that you think signifies the best,
> worst, or most obfuscated of your work, I'd love to have a copy for
> testing. Files written in non-English languages are a plus.
>
> I understand that in some projects these files are possibly quite
> secret, or are otherwise not to be thrown around - I don't want secrets,
> just files you're happy to let me see. These files won't go anywhere
> other than my own PC anyway; any failures will be made into their own
> unit tests.
>
> So, that's the call. Anyone up for it?
>
> Andrew
>
> >
>
I'm interested in your need to parse the file directly, can you elaborate on
that?

Alex

-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." --Voltaire
"The people's good is the highest law."--Cicero

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to