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
Change type and add _Py_ prefix to COUNT_ALLOCS variables #49100
Comments
quick_int_allocs, quick_neg_int_allocs, tuple_zero_allocs, and |
Attached patch is fairly straightforward with only one caveat: instead I am not proposing to move declarations to header files with this patch. |
Martin, Can you comment on whether unlist_types_without_objects should be global? Thanks. $ svn blame Objects/object.c | grep unlist_types_without_objects
45527 martin.v.loewis int unlist_types_without_objects; |
Making it static is fine. I don't recall what kind of customization I I'm skeptical about the entire issue, though. Why is it that these |
On 2009-01-06 11:28, Martin v. Löwis wrote:
For completeness and to make things easier for all developers, |
I don't think completeness is a useful thing to have here.
It is not easier, but more difficult. It now requires a change,
Ah - but they aren't exported symbols. |
On 2009-01-06 13:28, Martin v. Löwis wrote:
Sure it does: consistent rules always make things easier, since
I'm only referring to exported symbols. Static globals, of course, |
Ok, the symbols in question are not exported from pythonxy.dll. |
On 2009-01-06 14:22, Martin v. Löwis wrote:
Right, because for MS VC you have to explicitly mark symbols for However, they are still exported from the object files, so can cause On Unix, libpythonX.X.a always includes those symbols and they Even production builds contain a few such symbols which require
Here's the grep line I used for that: nm libpython2.6.a | egrep ' [TD] ([^P_]|P[^y]|_[^P])' | sort |
On Tue, Jan 6, 2009 at 7:28 AM, Martin v. Löwis <report@bugs.python.org> wrote:
I actually agree with Martin on this one. I would not touch this if |
On 2009-01-06 15:57, Alexander Belopolsky wrote:
I don't follow you: those symbols are not meant for public use anyway, |
On Tue, Jan 6, 2009 at 10:53 AM, Marc-Andre Lemburg
This is the same that I said: "renaming is cost free" if it is done |
Ah. Those are "global symbols", not "exported symbols"; "export"
See, and in this specific case, they can't, because they are used
No. They don't require the Py_ prefix, because they already |
On Wed, Jan 7, 2009 at 4:33 AM, Martin v. Löwis <report@bugs.python.org> wrote:
My main interest in this patch are the type and %d to %zd change, but I already stated that I am only +0 on the name change and that "+" is
That's true, but asdl_ prefix is not a well-known prefix reserved for Also a grep through nm output that Marc-Andre did is a good check to |
On 2009-01-07 10:33, Martin v. Löwis wrote:
Not at all. .so share libs and .a libs on Unix provide exports
Oh please. The convention is that *all* Python exported symbols The above symbols violate this convention, as do any symbols I consider it a bug that Python still exports symbols that |
I think it is indeed better to focus on this part of the patch only. I just reviewed it, and I think it is incorrect: We cannot assume that I fixed it, and removed the _Py_ prefixing, and committed the result
make smelly |
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: