Can we use tracing instead of env_logger ?

Can we use tracing instead of env_logger ?

Yes, there are list of loggers:

simple_logger
simplelog
pretty_env_logger
stderrlog
flexi_logger
call_logger
std-logger
structured-logger
log4rs
fern

You could visit page https://crates.io/crates/log and find all list of loggers

I was talking about the https://lib.rs/crates/tracing crate specifically :)

I was talking about the https://lib.rs/crates/tracing crate specifically :)

If you ask my opinion. I think, yes it is possible to use tracing libray for logging like log library.
But what I see:

1. I try to find tracing library using in project code. It is not look like simple logging
2. I never use tracing library in my project. If project manager of "hf-hub" make decision use tracing for logging. Then I could learn tracing library and change my pull request from log to tracing library.

I'll go ahead and merge for now, we can revisit later.

IMO this crate should be minimalistic, hence logging (and sparingly) should be OK.
Users can always trace themselves to the actual potential bottlenecks like get and download.
All other functions should be rather trivial.

For the record, I'm not happy about this 😄

tracing is a standard and used pretty much everywhere for logging. I think we should revisit eventually!

https://crates.io/crates/tracing (~200k/day)
https://crates.io/crates/log (~400k/day)

I don't care that much about it either way, ideally I think we just should just have neither, or behind feature flags.

Ah I didn't think log was as ubiquitous, looks like a sync vs async divide, tokio has a dependency on tracing while most sync libraries have log.

I also thought log had less features for libraries, but either I missed it at the time, either it caught up.

You live in async world ! :)