Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make black optional #23

Closed
wants to merge 1 commit into from
Closed

Make black optional #23

wants to merge 1 commit into from

Conversation

SuperSandro2000
Copy link

I am trying to reduce the usage of linting programs like black or isort in nixpkgs to make programs less likely to break when they are updated and they trigger fewer rebuilds.

I am trying to reduce the usage of linting programs like black or isort in nixpkgs to make programs less likely to break when they are updated and they trigger fewer rebuilds.
@Zac-HD
Copy link
Owner

Zac-HD commented Apr 4, 2022

Hi Sandro - I'm happy to reduce the installation dependencies, but Black is already only a test-time dependency and this is an important semantic test to run.

@Zac-HD Zac-HD closed this Apr 4, 2022
@SuperSandro2000
Copy link
Author

Nixpkgs runs tests to make sure the packages we ship are compatible. Black is a problematic dependency because if formatting changes in an update (which already happened a couple of times) tests fail for ignorable reasons. We then need to disable those tests for the builds to succeed. The best for us is when static analysis and linting tools are not run in test suites to make sure only actually breakages make the tests fail.

@Zac-HD
Copy link
Owner

Zac-HD commented Apr 5, 2022

Read the tests, they don't fail on formatting changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants