IDG SERPRO
IDG SERPRO
Will you follow up https://community.plone.org/t/zope-contributor-agreement-process/8495 in the future?
@gotcha RIght after https://github.com/buildout/buildout/blob/9ba1e3170a474e6139c9a7eadd32a498c22cb3bb/bootstrap/bootstrap.py#L77: ``` 74 │ options, args = parser.parse_args() 75 │ if options.version: 76 │ print("bootstrap.py version %s" % __version__) 77 │ sys.exit(0) ``` It would be nice...
In fact, [these changes](https://github.com/buildout/buildout/issues/444#issuecomment-508241803) are intended for poor souls in the future that may came across legacy systems and need to migrate. But since Python 2.x isn't oficially supported anymore......
@gotcha Thanks for the clarification. Since the motivation of the issue was the question answered in https://github.com/buildout/buildout/issues/444#issuecomment-702090411, can we close it?
If so, I think it's a good idea to put this information in the README as well.
If you think it's better to remove it from Plone 5 and leave at Plone 3 branch, that's fine. It's nice to be version independent but sometimes that's not possible,...
Shouldn't this be asked at mr.bob since we're messing with ini files? My 0.02c: - Set a bunch of environment variables somehow (for example, named MR_BOB_PLONE_VERSION), from Python code, and...
> Is there a special reason you need plone.restapi 7.3.5? AFAIK the latest Plone 4 compatible release 6.13.8 should work fine. (there's 6.14 and 6.15 which only add a new...
> Export the blob-path and load each blob from the filesystem. That could be quite efficient. This would be a "post-export" that would insert in the json, already on disk,...
> Feel free to improove it the way you like. Unfortunately since this package is in the `plone` namespace (a Contributor's Agreement is needed) and we still don't have it...