Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Don't gate IO libraries by default
See original GitHub issueGiven the presence of wheels for all 3 of our upstream IO libraries, I think it makes sense to favor convenience now and have pip install sgkit pull in the IO libraries by default.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Guide to Settings of Candlestick Charts - Gate.io
Set the starting time of the candlestick chart by clicking on the settings icon on the top-right corner. Indicators and features of candlestick...
Read more >IO Libraries Suite Downloads | Keysight
Download Keysight IO Libraries software. The updated IO Libraries Suite helps accelerate instrument connection and control. Learn more!
Read more >Displaying figures in Python - Plotly
Displaying Figures using Plotly's Python graphing library. New to Plotly? ... import plotly.io as pio pio.renderers.default = "browser".
Read more >Exchange-specific Notes - Freqtrade
Freqtrade is based on CCXT library that supports over 100 cryptocurrency exchange ... Gate.io supports stoploss_on_exchange and uses stop-loss-limit orders.
Read more >Extending with Shared Libraries - Jenkins
A Shared Library is defined with a name, a source code retrieval method such as by SCM, and optionally a default version. The...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Actually, no, it can be either. It turns out that we can have pre-releases packages it’s just that conda is hopeless with differentiating them from non-prereleases. But, if we only have pre-releases up there, then it should be fine.
So, the general rule is “don’t make pre-release conda packages”, but in this case it’ll be fine for us.
Probably the path of least resistance for us will be to make a bioconda package, which seems like the right thing to do given the dependencies. Windows users can use the pip package, which is fine I think.