Remove junk and unnecessary files from module

[Samrat-Revagade]

I can see a lot of unnessary files in the module please remove them
for example:

1. test.txt ? Do we need this ?
2. p1.py~ ? lokks like you have accidentally added swap file
3. report ? why we need this if this is an intermediate file which gets generated when module runs then you should delete this at the end .i.e when module finishes
4. report.pdf ? you github commit should not contain this file
5. recommend.txt ? again intermediate file
   6 postgresql.conf ? why this files is in github commit ?
6. postgre_info.pyc ? what is this file ? and why do we need this in commit ?
7. os.conf.pdf ? again intermediate file
8. os.conf ? again intermediate file
9. report.pdf ? we dont need this in github commit ? do we ?

The point I am trying to make is keep your code repository as clean as possible I am sure you can find more files like this if you look carefully at your code
please clean it

[Rushikesh005]

I have used report.txt file as intermediate file in between txt to pdf conversion.

[Rushikesh005]

ok , I will try to remove intermediate files os.conf, postgresql.conf, report.txt and recommend.txt on next commit.thank you

[Rushikesh005]

Is there any suitable location for report.pdf? Actually, I always commit
the whole directory each time. So, report.pdf gets pushed to github.
Any suggestions on locations of files [code/outputs]? I used src directory
for codes, Is it fine?. And as you mentioned, I handled intermediate files
so that they don't appear in main or src directory.

On Thu, Mar 27, 2014 at 11:38 AM, Samrat notifications@github.com wrote:

I can see a lot of unnessary files in the module please remove them
for example:

1. test.txt ? Do we need this ?
2. p1.py~ ? lokks like you have accidentally added swap file
3. report ? why we need this if this is an intermediate file which gets
   generated when module runs then you should delete this at the end .i.e when
   module finishes
4. report.pdf ? you github commit should not contain this file
5. recommend.txt ? again intermediate file
   6 postgresql.conf ? why this files is in github commit ?
6. postgre_info.pyc ? what is this file ? and why do we need this in
   commit ?
7. os.conf.pdf ? again intermediate file
8. os.conf ? again intermediate file
9. report.pdf ? we dont need this in github commit ? do we ?

The point I am trying to make is keep your code repository as clean as
possible I am sure you can find more files like this if you look carefully
at your code
please clean it

Reply to this email directly or view it on GitHubhttps://github.com//issues/9
.

[Samrat-Revagade]

Actually there is no such a need to include report.pdf file into the module as its o/p file.
If user want to see it he can get its live copy by actually running the module itself.

about using src directory is a good idea :) welcome to software world :)
now code looks much better :)