New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compiler package needs better documentation. #33512
Comments
The compiler package is not documented; this needs to be done before tools are likely to be written on top of it. |
Jeremy -- is there anything that can be done to make it easier for you to get this done? I think these should really be documented and moved into the library. |
Logged In: YES Jeremy said he'd work on this next week, so I'm bumping the |
Logged In: YES I'll note that Jeremy has written basic docs, and they are |
Logged In: YES jeremy, get your butt in gear on this! |
This is one of the oldest bugs we have... As the compiler package surely got revised with the inclusion of AST, and the bug was only to remember about polishing... this still needs to be open? |
The SVN log reflects that the docs *have* been moved into the Library Reference, and that they have been corrected and polished. Fred, you said they needed polishing in December 2001. From then, corrections have been made from Georg, Raymond, Brett and edloper. I'm closing this, but feel free to reopen it if you think that this docs *still* need more polishing. Regards, |
I think this is fine, Facundo. All docs need polishing, but that's not a bug so long as they're complete, accurate, and readable. Thanks for checking on this. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: