Iblis Lin
Iblis Lin
I think current `TimeArray` supports `Tables.jl` protocol already. So the output can be converted to `DataFrame` or `CSV` easily.
FYI: https://juliastats.org/TimeSeries.jl/dev/tables/
And about the issue: changing signature into the form `yahoo(ticker, opt, sink)`. > The problem with this direct approach is that it is very non-general. If in some other data...
> Well, here are some more thoughts in support of this proposal. > 1. Performance. ... > 2. Time array specialty. > 3. Human factor and other data sources. Ah,...
@Arkoniak I'm still busy on TimeSeries.jl (https://github.com/JuliaStats/TimeSeries.jl/issues/482). How about just go with your interface package (https://github.com/Arkoniak/ProtoMarketData.jl) right now? Maybe transfer it to this org and apply the new interface for...
well, `TimeArray` cannot have different type in single column, since the underlying implementation is `Matrix`. Although one can build an instance of `TimeArray{Union{Float64, String}, ...}`, that breaks almost all operations...
yeah, with the additional kwarg supported
(Let me re-read that issue again :p)
FYI: https://github.com/pellaeon/bsd-cloudinit/blob/master/cloudbaseinit/metadata/factory.py#L29
Hi @ntt1985 . Our scripts depends on some native extensions that need to be compiled during installation: - devel/py-babel - devel/py-greenlet - net/py-netifaces However, [we cannot compile softeware on pfSense.](https://doc.pfsense.org/index.php/Can_I_compile_software_on_pfSense)...