I suggest to disable the [X refs, Y blocks] ouput in debug builds by default, and provide an option to enable it if/when necessary.
Most of the time these values are not necessary, and they end up getting in the way while copy/pasting code from the interpreter and/or running tests (we even have a function in test.support to get rid of them).
They are sometimes useful while investigating refleaks, so there should still be an option to enable it. I'm not sure what would be the best way to do it (a new python flag?).

The "refs" output also complicates testing in some cases, e.g.

http://hg.python.org/cpython/file/bc4458493024/Lib/test/test_subprocess.py#l61
http://hg.python.org/cpython/file/bc4458493024/Lib/test/test_subprocess.py#l786

I don't know exactly what the option would be called, but +1 on the idea. Perhaps something under the interpreter's -X option since it's implementation-specific?

This output gets in the way a fair bit when debugging interpreter sessions, and Chris brings up a good point about testability.

Here's a proof of concept that defines a new _print_total_refs() function and calls it through the PRINT_TOTAL_REFS macro, disables printing the refs by default, and adds a "-X showrefcount" option to reenable it. This can also be achieved at runtime by adding/removing 'showrefcount' from the sys._xoptions dict.

Things that should be done/decided before the final version:

1. the function and/or prototype should probably be moved to a better place;
2. the 'showrefcount' name sounds ok to me, but I'm open to suggestions if you can come up with something better;
3. the function could do the equivalent of "if sys._xoptions.get('showrefcount', False):" instead of "if 'showrefcount' in sys._xoptions:";
4. now that this can be enabled/disabled at runtime, we might make it available to non-debug builds too (unless there are other negative side-effects);

_Py_GetRefTotal() wouldn't be available in non-debug builds IIRC.

Yes -- I was proposing to make it available on non-debug builds too, unless it has a negative impact on the performance or other similar issues.

If this is done, it should probably be on by default on all --with-pydebug buildbots. Otherwise I suspect nobody will _ever_ look at its output and we should just remove the feature all together.

Being off in the main process on the build bots would still make test_subprocess.py happier though as that test's own child processes wouldn't pass the command line flag to enable it so they wouldn't see it in child process stderr.

If this is done, it should probably be on by default on all
--with-pydebug buildbots.

With "on by default" you mean that the output should be disabled or enabled?

Otherwise I suspect nobody will _ever_ look at its output and we
should just remove the feature all together.

IME the refcount is only useful while trying things in the interactive interpreter manually, e.g. try to repeat the same operation and see if the refcount increases or not. In this case the feature would still be useful, so it should be kept.

Attached updated patch with docs and tests.
I changed the function to do the equivalent of "if sys._xoptions.get('showrefcount', False):" as proposed in msg183608.
Adding -X showrefcount to non-debug builds could be covered in a separate issue.
Cleaning up the test suite to avoid checking for the refcounts in stderr can also be done in a separate commit if necessary.

Attached a new patch that addresses a couple of minor things pointed out in the reviews.

New changeset 367167f93c30 by Ezio Melotti in branch 'default':
bpo-17323: The "[X refs, Y blocks]" printed by debug builds has been disabled by default. It can be re-enabled with the -X showrefcount option.
http://hg.python.org/cpython/rev/367167f93c30