[issue35718] Cannot initialize the "force" command-option

Opher Shachar added the comment: (from the PR11526) In this build_py subclass I initialize force to 1, but when reaching byte_compile() we find out it was reset to None. from setuptools.command.build_py import build_py as _build_py class build_py(_build_py): def initialize_options(self):

[issue35718] Cannot initialize the "force" command-option

Éric Araujo added the comment: Could you tell how you found the problem, i.e. what are you trying to do? -- ___ Python tracker ___ _

[issue35718] Cannot initialize the "force" command-option

Change by Opher Shachar : -- keywords: +patch, patch, patch, patch pull_requests: +11109, 0, 1, 2 stage: -> patch review ___ Python tracker ___ ___

[issue35718] Cannot initialize the "force" command-option

Change by Opher Shachar : -- keywords: +patch, patch, patch pull_requests: +11109, 0, 2 stage: -> patch review ___ Python tracker ___ _

[issue35718] Cannot initialize the "force" command-option

Change by Opher Shachar : -- keywords: +patch pull_requests: +11109 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-l

[issue35718] Cannot initialize the "force" command-option

Change by Opher Shachar : -- keywords: +patch, patch pull_requests: +11109, 0 stage: -> patch review ___ Python tracker ___ ___

[issue35718] Cannot initialize the "force" command-option

New submission from Opher Shachar : When creating a custom Command (or sub-classing one) we cannot initialize in "initialize_options()" the "force" option to 1, because Command.__init__ resets it to None after the call to self.initialize_options(). -- components: Distutils messages: 3