Jim Fulton

On Wed, Nov 10, 2021 at 3:53 PM Jason Madden ***@***.***> wrote: > OK, I think I'm allowed to relay this now: The company that I co-founded > and which...

Good answer. Thanks Marius. To elaborate a bit, catalogs are objects that maintain multiple indexes on a collection of objects. They provide for querying on one or more among multiple...

See: https://groups.google.com/forum/#!topic/buildout-development/bfGPpgirAhk IOW, if you get a conflict, try: bin/buildout extensions= to get buildout upgraded then run buildout as usual. I'm thinking that we should delay loading extensions until after...

No, I just happened to run into this yesterday on work for a customer. :) Bonus: https://github.com/pypa/setuptools/issues/997 I haven't used any extensions in quite a while, so this hasn't bitten...

@leorochael so if someone updates a buildout dependency and it's not pinned, buildout should fail? I don't like that idea. :) It also doesn't really solve a problem afaict. After...

@mdeguzis I don't understand what scenario you're describing.

Ah, thanks for reminding me. :) An issue with extensions like mr.developer, is that they're loaded before upgrading. Upgrading conforms buildout to its requirements, but extensions are loaded before it...

Note that currently, when doing a local bootstrap (from a virtualenv or local buildout), the paths to buildout and its dependencies come from the original locations, which means that buildouts...

I can't reproduce this with buildout 2.6.0 or 2.5.3 for the case when the buildout and virtualenv directories are different, because buildout won't upgrade if it's not in the buildout's...

BTW, the check for the buildout script outside the bin directory should be done first, as we can avoid checking for new revisions.