Re: [Python-Dev] Buildbot failures
On 10/21/2011 10:08 PM, Antoine Pitrou wrote: Hello, There are currently a bunch of various buildbot failures on all 3 branches. I would remind committers to regularly take a look at the buildbots, so that these failures get solved reasonably fast. Regards Antoine. In my previous workplace if someone broke a build committing something wrong he/she had to bring cake for everyone next meeting. The cake is not really feasible I guess, but isn't it possible to notify the developer that broke the build? If one is not clearly defined, maybe notifying the last N developers that committed between the last successful builds and the failing build, would it be possible and make sense? ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] #include "Python.h"
I have a newbie question about CPython. Looking at the C code I noted that for example in tupleobject.c there is only one include #include "Python.h" Python.h actually includes everything as far as I can I see so: - it's very hard with a not-enough smart editor to find out where the not-locally defined symbols are actually defined (well sure that is not a problem for most of the people) - if all the files include python.h, doesn't it generate very big object files? Or is it not a problem since they are stripped out after? Thanks, Andrea ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] #include "Python.h"
On 01/29/2012 05:22 PM, Oleg Broytman wrote: Hello. We are sorry but we cannot help you. This mailing list is to work on developing Python (adding new features to Python itself and fixing bugs); if you're having problems learning, understanding or using Python, please find another forum. Probably python-list/comp.lang.python mailing list/news group is the best place; there are Python developers who participate in it; you may get a faster, and probably more complete, answer there. See http://www.python.org/community/ for other lists/news groups/fora. Thank you for understanding. I wrote here because I thought it was the best place, but I understand this point of view, I can ask on python or python-core for example.. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] #include "Python.h"
On 01/29/2012 06:34 PM, Paul Moore wrote: On 29 January 2012 18:10, C. Titus Brown wrote: python-dev isn't that inappropriate, IMO, but probably the best place to go with this discussion is python-ideas. Could you repost over there? I agree that python-dev isn't particularly appropriate, python-list is probably your best bet. The python-ideas isn't really appropriate, as this isn't a proposal for a change to Python, but rather a question about how the Python C code is structured. That's always a grey area, and I can see why the OP thought python-dev might be a reasonable place. Ok well for this I won't repost it anywhere else, I have already all the answers I wanted and it was not so important.. Having said all that: Python.h actually includes everything as far as I can I see so: - it's very hard with a not-enough smart editor to find out where the not-locally defined symbols are actually defined (well sure that is not a problem for most of the people) Well, that's more of a question of what tools you use to edit/read Python code. I guess you could view it as a trade-off between ease of writing the core code and extensions (avoiding micromanagement of headers, and being able to document #include "Python.h" as the canonical way to get access to the Python API from C) versus tracking down macro definitions and symbol declarations (and that's really only for information, as the API is documented in the manuals anyway). I don't use an editor that can automatically find the definitions, but grep and the manuals does me fine. Yes sure it makes sense, probably it's even better than including only simple files, since all the contributions to Python.h can be moved around and refactored without breaking all the code.. And for editor I use Emacs, which can actually do any kind of magic on the symbols, I just didn't set it up for the python source code.. Thanks, Andrea ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Playing with a new theme for the docs
On 03/24/2012 03:30 AM, PJ Eby wrote: Weird - I have the exact *opposite* problem, where I have to resize my window because somebody *didn't* set their text max-width sanely (to a reasonable value based on ems instead of pixels), and I have nearly 1920 pixels of raw text spanning my screen. Bloody impossible to read that way. But I guess this is going to turn into one of those vi vs. emacs holy war things... (Personally, I prefer jEdit, or nano if absolutely forced to edit in a terminal. Heretical, I know. To the comfy chair with me!) Suppose the author set the size to 1000 pixels, you would end up with 920 white pixels on the side, does it make sense? Using a tiling window manager (for example awesome or xmonad) would solve your problem in a more definitive way imho than hoping in the web designer choices.. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
