Skip to content

bpo-33311: Do not display parameters displayed in parentheses for module call #6522

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

Closed
wants to merge 45 commits into from

Conversation

sblondon
Copy link
Contributor

@sblondon sblondon commented Apr 18, 2018

This PR removes the parentheses if the trace is in module directly.
The parentheses and parameters are kept otherwise.

There is a potential conflict with the fix in bpo-3356 because there is one line modified by each pull-request (in the html() function).

https://bugs.python.org/issue33311

sblondon and others added 27 commits April 18, 2018 20:50
python#6519)

Converting with line_info=False and col_info=True crashed before.
as docstrings and translatable strings, and rejects
bytes literals and f-string expressions.
…6537)

Fix clang ubsan (undefined behavior sanitizer) warnings in dictobject.c by
adjusting how the internal struct _dictkeysobject shared keys structure is
declared.

This remains ABI compatible.  We get rid of the union at the end of the
struct being used for conveinence to avoid typecasting in favor of char[]
variable length array at the end of a struct. This is known to clang to be
used for variable sized objects and will not cause an undefined behavior
problem.  Similarly, char arrays do not have strict aliasing undefined
behavior when cast.

PEP-007 does not currently list variable length arrays (VLAs) as allowed
in our subset of C99.  If this turns out to be a problem, the fix to this is
to change the char `dk_indices[]` into `dk_indices[1]` and restore the
three size computation subtractions this change removes:
  `- Py_MEMBER_SIZE(PyDictKeysObject, dk_indices)`

If this works as is I'll make a separate PR to update PEP-007.
…ILD_CORE (pythonGH-6489)

Setup modules are no longer built with -DPy_BUILD_CORE by default,
as using that flag may now require including additional internal-only header files.

Instead, only the modules that specifically need it use that setting.
This change contains minor things that make diffing between Lib/tokenize.py and
Lib/lib2to3/pgen2/tokenize.py cleaner.
)

Starting with glibc 2.27.9000-xxx, sigaddset() can return EINVAL for some
reserved signal numbers between 1 and NSIG.  The `range(1, NSIG)` idiom
is commonly used to select all signals for blocking with `pthread_sigmask`.
So we ignore the sigaddset() return value until we expose sigfillset()
to provide a better idiom.
python#6446)

* bpo-33251: ConfigParser.items no longer returns items present in vars.

Documentation for `ConfigParser.items()` states:
'Items present in vars no longer appear in the result.'

This fix aligns behaviour to that specified in the documentation.
pythonGH-6273)

External importers were being added in both phases of the import
system initialisation.

They're only supposed to be added in the second phase, after the
import machinery has been appropriately configured.
vstinner and others added 13 commits April 27, 2018 14:30
Cast pointer difference from ssize_t to int: a frame is very unlikely
larger than 2 GB.
…RGS. (pythonGH-6030)

METH_NOARGS functions need only a single argument but they are cast
into a PyCFunction, which takes two arguments.  This triggers an
invalid function cast warning in gcc8 due to the argument mismatch.
Fix this by adding a dummy unused argument.
@sblondon sblondon requested a review from a team April 30, 2018 22:07
@sblondon sblondon requested a review from a team as a code owner April 30, 2018 22:07
@the-knights-who-say-ni
Copy link

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately our records indicate you have not signed the CLA. For legal reasons we need you to sign this before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

When your account is ready, please add a comment in this pull request
and a Python core developer will remove the CLA not signed label
to make the bot check again.

Thanks again to your contribution and we look forward to looking at it!

@sblondon sblondon changed the title bpo-33311: Parameters displayed in parentheses are not displayed for module call bpo-33311: Do not display parameters displayed in parentheses for module call Apr 30, 2018
@sblondon
Copy link
Contributor Author

Sorry for the noise: I guess I made a mistake: I wanted to rebase this patch in order to fix the conflict with the patch attached to bpo-3356 (which is in master branch now).

  • the conflict is solved
  • however, the commits added by the rebase are added to the PR. I have no idea how I can fix that (in case it would be possible).

Perhaps, the simplest solution is to remove this branch and create another one?

@gvanrossum
Copy link
Member

Close the issue and start a new one.

@brettcannon brettcannon closed this May 1, 2018
@sblondon sblondon deleted the no-parentheses-for-module-call branch May 1, 2018 20:47
@terryjreedy terryjreedy removed their request for review May 16, 2018 02:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.