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
Change by Opher Shachar :
--
keywords: +patch
pull_requests: +11109
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35718>
___
___
Py
Change by Opher Shachar :
--
keywords: +patch, patch
pull_requests: +11109, 0
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Opher Shachar :
--
keywords: +patch, patch, patch
pull_requests: +11109, 0, 2
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Opher Shachar :
--
keywords: +patch, patch, patch, patch
pull_requests: +11109, 0, 1, 2
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
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
