Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings
Discussion options

jtroe
May 14, 2025

As a user, I would like to be able to specify a package I would like, and manually manage dependencies.

e.g. in pyscript.toml

packages = ["arcgis --no-deps"]

(or whatever syntax makes the most sense, if it becomes an object or something)

from python, I can use micropip to install the package (it is failing to import after this, but I'm confident there is a way to make it work)

import pyodide_js
await pyodide_js.loadPackage('micropip')
import micropip
await micropip.install("arcgis >=2.4.1", deps=False)
import arcgis # fails currently, may need to do the install on js before loading the script

Similar issue: #2298
You must be logged in to vote

Replies: 1 comment · 5 replies

Comment options

WebReflection
May 15, 2025
Maintainer

I am personally not too keen to find a solution that works for only 1 out of many fields micropip.install accepts:
https://micropip.pyodide.org/en/v0.7.1/project/api.html#micropip.install

I actually wonder if having something like this would be a nice addition to our packages featutres/abilities:

[package.arcgis]
version=">=2.4.1" # optional
keep_going=False # optional
deps=True # optional
credentials=None # optional
pre=False # optional
index_urls=None # optional
verbose=None # optional

A list of package.xxxx could be available and power-users would have full control over these details ... heck this could also be parsed before regular packages, when present, to ensure that if further packages have dependencies these are already available ... would that make sense or be useful?
You must be logged in to vote
5 replies
@jtroe
Comment options

jtroe May 15, 2025
Author

I like that solution
@jtroe
Comment options

jtroe May 15, 2025
Author

Something else that might work for my use case is being able to specify packages to mock in the config.
@WebReflection
Comment options

WebReflection May 15, 2025
Maintainer

please let's have one discussion per time 😅
@jtroe
Comment options

jtroe May 15, 2025
Author

Seemed relevant 🤷‍♂️
@WebReflection
Comment options

WebReflection May 15, 2025
Maintainer

you can mock via index_urls as long as that provide the related mock so it should work out of the box but right now I'd like to focus on the requirement and the proposed solution which should solve the requirement ... mocks are not into the requirement, it was actually just deps which is why I'd like not to mix topics and find something that could work across interpreters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
@jtroe @WebReflection
Morty Proxy This is a proxified and sanitized view of the page, visit original site.