Put expose classes at an independent package

[GoogleCodeExporter]

Expose classes adds dependencies for Django and others when they are not always 
necesary. I propose to put it at an independent 'expose' egg/deb package being 
the PyFilesystem core a dependency of it.

Original issue reported on code.google.com by piranna on 2 Mar 2012 at 9:40

[GoogleCodeExporter]

I'm not sure if pyfilesystem is really big enough to warrant being split into 
multiple parts.
Would this problem 'go away' if Issue 99 got fixed?

Original comment by gc...@loowis.durge.org on 24 Aug 2012 at 10:31

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

My intention was more related to the fact that the pyfilesystem package is too 
big for embebed platforms like PyMite and have too much specialized filesystems 
with external dependencies, so my idea was to have a package with all the core 
and base classes and another one for the implementations, so they could be able 
to download and update independent.

Original comment by piranna on 24 Aug 2012 at 11:15

[GoogleCodeExporter]

We could extract expose and put it in a separate package, but that would 
inconvenience that majority of users who need expose or don't mind it being 
there.

If someone really needs a cut down PyFilesystem without expose, then it is a 
tiny amount of effort to delete a folder and maybe remove the dependancies from 
setup.py.

Original comment by willmcgugan on 24 Aug 2012 at 11:22

• Changed state: WontFix

[GoogleCodeExporter]

"have a package with all the core and base classes and another one for the 
implementations"
and there's absolutely nothing stopping you doing that ;-) It's entirely up to 
you which code from pyfilesystem gets placed into which (distro-specific) 
packages.

Original comment by gc...@loowis.durge.org on 24 Aug 2012 at 11:37

[GoogleCodeExporter]

Well, it's true... i was hopping some official support... :-D

Original comment by piranna on 24 Aug 2012 at 11:57