Skip to content

Enforce PEP-8 guidelines in the Python Codebase #762

Closed

Description

@vybhav72954

@HarshCasper The name is obvious in itself, this is in conjunction with #688

I will open a PR after I refactor at least 10 directories, so as not to simply clutter up the Issues and PRs.

Or shall I do it in one go?

Activity

  1. HarshCasper commented on Feb 14, 2021

    @HarshCasper
    Owner

    Please go ahead. Just use the /assign bot and feel free to work on any improvements 😄

  2. pganguli commented on Mar 2, 2021

    @pganguli
    Contributor

    In pull request #804, @vybhav72954 mentioned that there are still around 50% formatting issues left to correct. If no further work is being done on this, I'd be happy to take over from where it was left off and (hopefully) close this issue. @HarshCasper I'm asking for this assignment for GSOOC'21.

  3. vybhav72954 commented on Mar 2, 2021

    @vybhav72954
    CollaboratorAuthor

    @pganguli Thanks for reminding me, I will open a separate issue, say by tomorrow, explaining what is left, you can take that issue by using /assign.

    @HarshCasper How does this sounds to you, you can close this issue as well, while I will open a new one explaining what we are lacking.

  4. pganguli commented on Mar 2, 2021

    @pganguli
    Contributor

    @pganguli Thanks for reminding me, I will open a separate issue, say by tomorrow, explaining what is left, you can take that issue by using /assign.

    @HarshCasper How does this sounds to you, you can close this issue as well, while I will open a new one explaining what we are lacking.

    Thanks. A description of what's left to be done will help me a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions