Pluto package manager & Pkg.develop

[aplavin]

I'm curious, what was the motivation to disable PlutoPkg when a package is developed manually?

Pluto.jl/src/packages/Packages.jl

Lines 20 to 23 in 163b7ce

	Symbol("Pkg.develop") ∈ node.references ||
	Symbol("Pkg.API.develop") ∈ node.references ||
	Symbol("Pkg.add") ∈ node.references ||
	Symbol("Pkg.API.add") ∈ node.references ||

I use Pluto + Pkg.develop together and didn't observe any issues yet. It's just somewhat inconvenient to sidestep the above check with:

import Pkg
dev = Pkg.develop
dev(path=".. path to mypackage ...")

using mypackage
using otherpackages  # managed by pluto

[fonsp]

I was unsure about it, and did not yet think through all possible use cases and edge cases, so I disabled it to avoid a difficult backwards-compat situation later.

The goal for now is: use plutopkg if and only if a notebook does not set up a package environment itself. That is simple logic to maintain, and simple for users to understand.

Eventually, I want to make develop possible through the GUI.

[aplavin]

Thanks for taking the time to respond even when on holidays :)
Indeed, being conservative first and potentially adding stuff later is probably better than the other way round. Just had to report that dev seems to work just fine already - but of course I didn't test all possible corner cases.
Looking forward to a Pluto-style gui for this!

[liuyxpp]

I would also like that Pkg.add a not-yet-registered URL package not to disable the Pluto package manager.

[BioTurboNick]

I've been finding myself wanting this. For now I've just been making use of many point releases (in private registry) to use it with PlutoPkg but that's not a great solution.

But, I appreciate finding the workaround noted in the first post.

[fonsp]

With JuliaLang/Pkg.jl#3783 we can describe local and git packages in Project.toml :)