Skip to content
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

Variable defined with initial += is undefined and .installed.cfg corrupted #641

Open
distributist opened this issue Jan 29, 2024 · 0 comments · May be fixed by #643
Open

Variable defined with initial += is undefined and .installed.cfg corrupted #641

distributist opened this issue Jan 29, 2024 · 0 comments · May be fixed by #643

Comments

@distributist
Copy link

A variable which is initially defined with += will end up with the variable undefined, or missing the initial definition. This is most likely to happen in complex buildouts with multiple overrides.

Such a case will corrupt .installed.cfg by adding an unparsable line "var + = base0" to the end of the offending part:

[base1]
__buildout_installed__ = 
__buildout_signature__ = wheel-339de3cbbb8d2a18c6d8133fb43aa777 zc.buildout-1a1dfc3477a86238088ba01adcf15436 pip-339de3cbbb8d2a18c6d8133fb43aa777 setuptools-339de3cbbb8d2a18c6d8133fb43aa777
recipe = zc.buildout:debug
var + = base0
distributist pushed a commit to distributist/buildout3-PATCHES that referenced this issue Jan 29, 2024
the initial definition, as if = was used (-= simply deletes the definition),
otherwise it will corrupt the .installed.cfg file. Fixes issue buildout#641.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant