Skip to content

Highlight when instantiate is called on an empty env#4601

Open
IanButterworth wants to merge 2 commits intoJuliaLang:masterfrom
IanButterworth:ib/instantiate_empty_warn
Open

Highlight when instantiate is called on an empty env#4601
IanButterworth wants to merge 2 commits intoJuliaLang:masterfrom
IanButterworth:ib/instantiate_empty_warn

Conversation

@IanButterworth
Copy link
Member

Because the user probably forgot to use --project etc. and is unknowingly instantiating the empty default env on CI.

@visr
Copy link
Contributor

visr commented Jan 27, 2026

Currently if you call instantiate on an empty environment, it writes only a Manifest.toml the first time, and adds a Project.toml the next time. That is probably unintentional, and I guess with this it would never write either.

I wonder how one is supposed to write empty projects though. In the context of #4473 it would be nice to be able to init an env, since a CLI call to activate doesn't have side effects. So I do activate followed by instantiating twice 😅. Not that that should be relied upon or block this PR, just wanted to mention it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: New

Development

Successfully merging this pull request may close these issues.

2 participants