Remove doc strings but not asserts from compiled CPython

Question

I want to remove doc strings from a Python program but leave asserts (and __debug__ sections) in. I have been using the -OO flag to generate .pyo files but according to the documentation that removes both asserts and doc strings.

I'm using CPython 2.7.

Clarification: I'm removing the docstrings as a cheap obfuscation method. Management made that decision and I think whether that is a useful thing to do is outside the scope of this question.

Why? o_O That seems like an odd requirement.

Amber
– Amber

2012-07-15 23:51:03 +00:00
Commented Jul 15, 2012 at 23:51 — Amber
– Amber, Commented Jul 15, 2012 at 23:51
+1, I would like a possibility to do this too

Dima Tisnek
– Dima Tisnek

2013-06-28 12:14:09 +00:00
Commented Jun 28, 2013 at 12:14 — Dima Tisnek
– Dima Tisnek, Commented Jun 28, 2013 at 12:14
Relevant to: stackoverflow.com/q/1273211/1959808

0 _
– 0 _

2017-09-29 08:28:07 +00:00
Commented Sep 29, 2017 at 8:28 — 0 _
– 0 _, Commented Sep 29, 2017 at 8:28

Ned Batchelder · Accepted Answer · 2012-07-16 00:30:59Z

3

You can't have half of -O. It removes docstrings and asserts, that's just the way it works. Asserts are usually written to be optional anyway, that is, you can remove them without affecting the behavior of the program.

If I had to remove docstrings and leave all else alone, I would consider writing a tool that opened .pyc files, unmarshaled the contents, modified them (by removing the docstrings), and repacked them as .pyc files. But that would likely be a delicate and fragile tool, if it can even be done that way.

edited Jul 16, 2012 at 0:30

answered Jul 16, 2012 at 0:07

Ned Batchelder

378k77 gold badges583 silver badges675 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Peter Graham Over a year ago

I've explained why I need to remove docstrings but not asserts in the question.

DaveP Over a year ago

Surely it would be much easier and quite robust to write a script to scrub the docstrings from the source files before they are compiled.

Sven Marnach Over a year ago

@PeterGraham: You didn't explain why you want to keep the asserts – and this is the really odd part of your requirements. Asserts are not meant to be needed in production builds.

0 _ Over a year ago

There are good reasons to keep assertions in production builds, especially of flight code. See: stackoverflow.com/a/29741912/1959808

Collectives™ on Stack Overflow

Remove doc strings but not asserts from compiled CPython

1 Answer 1

4 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related