Skip to content

Suppressing CIFAR uninformative and annoying download notification #8680

@talcs

Description

@talcs

🚀 The feature

The download method at the CIFAR datasets prints to STDOUT Files already downloaded and verified whenever CIFAR10 or CIFAR100 is initiated with download=True.

This is in contrast to other datasets, like MNIST or FashionMNIST, where nothing is printed if the files are already there.

Motivation, pitch

  • One of the scenarios of using the download=True flag is when you want the files to be downloaded on the first time, and then reused on other times. It should mean "Only download if something is missing". So using download=False would be a suboptimal workaround.
  • Why not always print a message to STDOUT for any operation that succeeds... (like moving a tensor to the GPU, loading data batches, computing loss)? For the same reason it shouldn't be printed here... Seriously, printing INFO log messages directly to STDOUT, while ignoring logging settings, is a bad practice. If the user has chosen a high-verbosity logging settings, then this is okay, but otherwise it is annoying.
  • When running massive experiments, this message contaminates the logs with uninformative text.
  • This is a little issue of annoyance, but it is clearly a bad practice.

Alternatives

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions