[Mesa-dev] Cleaning up Python scripts
stereotype441 at gmail.com
Wed Sep 14 08:54:42 PDT 2011
On 14 September 2011 08:26, Corbin Simpson <mostawesomedude at gmail.com>wrote:
> I've talked about it a bit before, but I feel that it's getting out of
> hand, so it's time to talk about cleaning up some of the Python that's
> used to generate/build Mesa.
> First, the biggest problem is that our Python's completely untested
> and unstructured. It's very ad-hoc. This might be alright for some of
> the codegen, but the rather extensive total weight of all of these
> scripts is over 20 KLOCs, and this is just too much code to be
> scattered about with very little organization. There are zero Python
> packages (folders with __init__.py) in Mesa.
> Here are a handful of problems exposed by pyflakes, a minimal static
> analysis tool which only catches syntax errors, unused names, and
> undefined names. This is really only tip-of-the-iceberg stuff, but I
> don't feel comfortable sending patches for this stuff without talking
> to the people that wrote this code originally.
> * /src/gallium/drivers/llvmpipe/lp_tile_shuffle_mask.py has a syntax
> error in global scope; it can't possibly run.
> * /scons/wcesdk.py has an undefined name in what appears to be dead
> code. This probably isn't a problem because I don't think any of us
> care about WinCE. (Which leads to the question: Why is this in the
> * /src/mapi/glapi/gen/*.py have undefined calls to show_usage(),
> which I anticipate should show a usage message and exit. However,
> since these are generally only called from Makefiles, they shouldn't
> be a problem. Of course, people might have trouble running them
> * /src/mapi/mapi/mapi_abi.py has a couple more undefined names in error
> What are people's opinions on this? Is it worth spending some time to
> clean up some of this code?
I'm generally in favor of clean-up, especially when it (a) fixes
rarely-encountered bugs, (b) improves clarity, or (c) increases the number
of people who understand a given piece of code. I'm not sure we'll get too
much of (a) in this case (since most of the code is only used at compile
time and always acts on the same input, every bug is either common or
benign), but we can probably get a lot of benefit in the (b) and (c)
Also, Python 3 is slowly taking hold (it's already the standard Python in
archlinux, and I expect others to follow), so some time in the next year or
so we might want to upgrade our Python scripts to use Python 3. It would be
nice to do a round of clean-up before we attempt that.
I've done professional Python development in the past, so I will try to help
with code review.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mesa-dev