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

Using development version of package opens Julia REPL #451

Closed
MilesCranmer opened this issue Feb 7, 2024 · 4 comments
Closed

Using development version of package opens Julia REPL #451

MilesCranmer opened this issue Feb 7, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@MilesCranmer
Copy link
Contributor

Affects: JuliaCall

Describe the bug

If I add a development dependency to my juliapkg.json, and then import my Python package, the Julia REPL will open. For example, on the pythoncall-try-3 branch of PySR, I modified juliapkg.json as follows:

{
    "julia": "1.6",
    "packages": {
        "SymbolicRegression": {
            "uuid": "8254be44-1295-4e6a-a16d-46603ac705cb",
            "dev": true,
            "path": "../SymbolicRegression.jl"
        },
        "ClusterManagers": {
            "uuid": "34f1f09b-3a8b-5176-ab39-66d58a4d544e",
            "version": "0.4"
        }
    }
}

I then install PySR and do import pysr. This gives me the following:

Screenshot 2024-02-07 at 14 28 52

I am able to exit the Julia REPL which returns me to the Python REPL.

I tried with the version of PythonCall.jl in main and I still see this issue.

@MilesCranmer
Copy link
Contributor Author

@cjdoris Seems like the same thing also happens when specifying a particular revision of a Git repository.

@MilesCranmer
Copy link
Contributor Author

Can a fix for this be back ported to 0.9?

@cjdoris
Copy link
Collaborator

cjdoris commented Feb 22, 2024

The main branch is 0.9.

I thought I fixed this on main a while back. Can you check again? If seems really weird that it would only happen for dev packages. Maybe juliapkg is not getting the version of PythonCall you think it's getting?

@MilesCranmer
Copy link
Contributor Author

I haven’t seen this issue ever since. It must have been an old package. Closing until it reappears..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants