You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
circup install -r would pick those as pywin32;platform_system, etc.
Would it be a good idea to:
have circup find and read the platform_system parameter (and ignore the module)
use a platform_system=='circuitpython' to specify modules that pip will ignore, but circup still install
This would allow pip and circup requirements to live in the same file to some extent for, say a project that is to be deployed on both a host and a target board. (For example circup itself can be a requirement for the host). Modules without a platform_system specified would still be installed (or ignored if known) as usual.
The text was updated successfully, but these errors were encountered:
Interestingly since circup cuts the line at the == sign to ignore the version, this format works to have the module ignored by pip and installed by circup.
There is an interesting and related discussion on my Gist from 2021 about how maybe (someday) you could use pip to install to circuitpython libraries onto boards.
Pip uses the following notation for platform-specific modules:
circup install -r
would pick those aspywin32;platform_system
, etc.Would it be a good idea to:
platform_system=='circuitpython'
to specify modules that pip will ignore, but circup still installThis would allow pip and circup requirements to live in the same file to some extent for, say a project that is to be deployed on both a host and a target board. (For example circup itself can be a requirement for the host). Modules without a platform_system specified would still be installed (or ignored if known) as usual.
The text was updated successfully, but these errors were encountered: