Skip to content

2 Graph folders #119

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

Closed
AnupKumarPanwar opened this issue Sep 28, 2017 · 6 comments · Fixed by #148
Closed

2 Graph folders #119

AnupKumarPanwar opened this issue Sep 28, 2017 · 6 comments · Fixed by #148

Comments

@AnupKumarPanwar
Copy link
Member

There are 2 separate folder of Graph

  1. Graph
  2. Data Structures - > Graph

Merge them and keep the second one

@CaptainAshis
Copy link

Hi Anup ,May be I'm asking a really stupid question but I have a doubt . You want this folder thing to be done in github right ? Or is it in some location in your computer drive . Just wanted some clarification .

@dynamitechetan
Copy link
Member

in the python repository, there is a graph folder and another folder called Data Structures - > Graph.
You need to merge them.
Clone this repo move the content of the folders and send a PR.

@iharsh234
Copy link

@AnupKumarPanwar #120 is merged, can you please close this :)

@AnupKumarPanwar
Copy link
Member Author

The "data_structures/Graph/" still not properly merged.
There are 2 copies of same algo :-

Breadth_First_Search.py
Deep_First_Search.py

P01_BreadthFirstSearch.py
P02_DepthFirstSearch.py

@iharsh234
Copy link

@AnupKumarPanwar so do we suppose to delete both?

P01_BreadthFirstSearch.py
P02_DepthFirstSearch.py

@luisiestrada
Copy link

It seems like Breadth_First_Search.py and Deep_First_Search.py have some syntax issues.
P01_BreadthFirstSearch.py and P02_DepthFirstSearch.py can run and are documented.
Which two should be deleted? How would you like these programs to be merged?

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

Successfully merging a pull request may close this issue.

5 participants