Change package structure

[GoogleCodeExporter]

Organize the modules into packages with the following structure:

atom
  - atom.py
  - app_servive.py

gdata
  - gdata.py
  - gdata_service.py
  gbase
    - gbase.py
    - gbase_service.py
  gcalendar
    - gcalendar.py
    - gcalendar_service.py
...

Original issue reported on code.google.com by api.jscu...@gmail.com on 3 Apr 2007 at 12:23

[GoogleCodeExporter]

Original comment by api.jscu...@gmail.com on 5 Apr 2007 at 9:23

• Changed state: Accepted

[GoogleCodeExporter]

Here is a new proposal for the full structure for the download:

README.txt
setup.py
...
src
  atom
    - atom.py
    - app_service.py
  gdata
    - gdata.py
    - gdata_service.py
    gbase
      - gbase.py
      - gbase_service.py
    gcalendar
      ...
    gspreadsheet
      ...
tests
  atom
    ...
  gdata
    ...
    gbase
      ...
    gcalendar
      ...
    gspreadsheet
      ...
samples
  base
    ...
  spreadsheets
    ...
  calendar
    ...

Original comment by api.jscu...@gmail.com on 5 Apr 2007 at 9:29

[GoogleCodeExporter]

After talking this over with a couple of people, I'm thinking of having a 
shallower 
directory structure.

Should I keep the src directory?

setup.py
src
  google
    __init__.py
    atom.py
    app_service.py
    gdata.py
    gdata_service.py
    gcalendar.py
    gcalendar_service.py
    ...
tests
  atom_test.py
  app_service_test.py
  gdata_test.py
  ...
samples
  base
    ...
  spreadsheets
    ...
  calendar
    ...

Original comment by api.jscu...@gmail.com on 13 Apr 2007 at 4:41

[GoogleCodeExporter]

see discussion thread 
http://groups.google.com/group/gdata-python-client-library-
contributors/browse_frm/thread/c3b3b7285c77b8d1

Original comment by api.jscu...@gmail.com on 17 Apr 2007 at 5:47

• Added labels: Milestone-Release1.0.1
• Removed labels: Milestone-Release1.1

[GoogleCodeExporter]

Original comment by api.jscu...@gmail.com on 21 Apr 2007 at 4:35

• Changed state: Verified