configobj-develop

[Configobj-develop] Can't easy_install ConfigObj for Python 2.5

[Robin M. <rob...@gm...>]

"easy_install ConfigObj" doesn't work if you're using Python 2.5.
There's no .egg for 2.5 linked from the
http://www.python.org/pypi/ConfigObj/ page, so setuptools downloads
the source and tries to run "setup.py -q bdist_egg --dist-dir
/tmp/easy_install-kjBHsO/egg-dist-tmp-wnCMdZ" instead. But that fails
with TypeError: "compile() expected string without null bytes". When I
run the same setup.py command by hand from inside the configobj-4.3.2
directory, I get:

usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
   or: setup.py --help [cmd1 cmd2 ...]
   or: setup.py --help-commands
   or: setup.py cmd --help

error: invalid command 'bdist_egg'

What would it take to get ConfigObj using a setup.py that's setuptools-aware?

-- 
Robin Munn
Rob...@gm...
GPG key 0x4543D577

Re: [Configobj-develop] Can't easy_install ConfigObj for Python 2.5

[Michael F. <fuz...@vo...>]

Robin Munn wrote:
> "easy_install ConfigObj" doesn't work if you're using Python 2.5.
> There's no .egg for 2.5 linked from the
> http://www.python.org/pypi/ConfigObj/ page, so setuptools downloads
> the source and tries to run "setup.py -q bdist_egg --dist-dir
> /tmp/easy_install-kjBHsO/egg-dist-tmp-wnCMdZ" instead. But that fails
> with TypeError: "compile() expected string without null bytes". When I
> run the same setup.py command by hand from inside the configobj-4.3.2
> directory, I get:
>
> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
>    or: setup.py --help [cmd1 cmd2 ...]
>    or: setup.py --help-commands
>    or: setup.py cmd --help
>
> error: invalid command 'bdist_egg'
>
> What would it take to get ConfigObj using a setup.py that's setuptools-aware?
>   

Hello Robin,

I think that to use ConfigObj with Python 2.5 you will need the version 
from subversion anyway. There is a rogue '__future__' important which is 
in the right place in subversion, but in the wrong place in the latest 
release.

I should probably do a new release because Nicola has made several good 
changes since the last release. I've been very distracted recently though.

As for eggs... well seeing that installing ConfigObj is a difficult as 
dropping one file somewhere on your path I never got round to doing 
that. I only uploaded the 2.4 eggs to stop the turbogears folk crying. ;-)

As setuptools seems to be maturing nicely (and is very nice to use) I 
should probably fix this. I'll be going to a setuptools talk at PyCon, 
so hopefully this will motivate me to sort it out.

All the best,


Michael Foord
http://www.voidspace.org.uk/python/articles.shtml

Re: [Configobj-develop] Can't easy_install ConfigObj for Python 2.5

[Jorge V. <jor...@gm...>]

On 1/31/07, Michael Foord <fuz...@vo...> wrote:
>
> Robin Munn wrote:
> > "easy_install ConfigObj" doesn't work if you're using Python 2.5.
> > There's no .egg for 2.5 linked from the
> > http://www.python.org/pypi/ConfigObj/ page, so setuptools downloads
> > the source and tries to run "setup.py -q bdist_egg --dist-dir
> > /tmp/easy_install-kjBHsO/egg-dist-tmp-wnCMdZ" instead. But that fails
> > with TypeError: "compile() expected string without null bytes". When I
> > run the same setup.py command by hand from inside the configobj-4.3.2
> > directory, I get:
> >
> > usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
> >    or: setup.py --help [cmd1 cmd2 ...]
> >    or: setup.py --help-commands
> >    or: setup.py cmd --help
> >
> > error: invalid command 'bdist_egg'
> >
> > What would it take to get ConfigObj using a setup.py that's
> setuptools-aware?
> >
>
> Hello Robin,
>
> I think that to use ConfigObj with Python 2.5 you will need the version
> from subversion anyway. There is a rogue '__future__' important which is
> in the right place in subversion, but in the wrong place in the latest
> release.
>
> I should probably do a new release because Nicola has made several good
> changes since the last release. I've been very distracted recently though.
>
> As for eggs... well seeing that installing ConfigObj is a difficult as
> dropping one file somewhere on your path I never got round to doing
> that. I only uploaded the 2.4 eggs to stop the turbogears folk crying. ;-)


if that's the case then let me cry for 2.5 eggs too :D

ConfigObj and ruledispatch are the only ones missing, and since pyrex is out
all we need for rule dispatch is see if it compiles
http://docs.turbogears.org/1.0/Python2.5Support


As setuptools seems to be maturing nicely (and is very nice to use) I
> should probably fix this. I'll be going to a setuptools talk at PyCon,
> so hopefully this will motivate me to sort it out.
>
> All the best,
>
>
> Michael Foord
> http://www.voidspace.org.uk/python/articles.shtml
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>

Re: [Configobj-develop] Can't easy_install ConfigObj for Python 2.5

[Robin M. <rob...@gm...>]

On 2/1/07, Jorge Vargas <jor...@gm...> wrote:
> > As for eggs... well seeing that installing ConfigObj is a difficult as
> > dropping one file somewhere on your path I never got round to doing
> > that. I only uploaded the 2.4 eggs to stop the turbogears folk crying. ;-)
>
> if that's the case then let me cry for 2.5 eggs too :D

Seconded (or re-seconded? since I was the original poster). I first
noticed the missing 2.5 eggs problem because of
http://docs.turbogears.org/1.0/Python2.5Support too. I'd really like
to see TurboGears with complete 2.5 ability, and that means bringing
ConfigObj up to speed.

Pretty please? :-)

-- 
Robin Munn
Rob...@gm...
GPG key 0x4543D577

Re: [Configobj-develop] Can't easy_install ConfigObj for Python 2.5

[Michael F. <fuz...@vo...>]

Robin Munn wrote:
> On 2/1/07, Jorge Vargas <jor...@gm...> wrote:
>   
>>> As for eggs... well seeing that installing ConfigObj is a difficult as
>>> dropping one file somewhere on your path I never got round to doing
>>> that. I only uploaded the 2.4 eggs to stop the turbogears folk crying. ;-)
>>>       
>> if that's the case then let me cry for 2.5 eggs too :D
>>     
>
> Seconded (or re-seconded? since I was the original poster). I first
> noticed the missing 2.5 eggs problem because of
> http://docs.turbogears.org/1.0/Python2.5Support too. I'd really like
> to see TurboGears with complete 2.5 ability, and that means bringing
> ConfigObj up to speed.
>
> Pretty please? :-)
>
>   
Ok, I'll look at getting a new release with 2.5 support and Nicola's new 
features done over the weekend.

Michael

Re: [Configobj-develop] Can't easy_install ConfigObj for Python 2.5

[Michael F. <fuz...@vo...>]

Robin Munn wrote:
> On 2/1/07, Jorge Vargas <jor...@gm...> wrote:
>   
>>> As for eggs... well seeing that installing ConfigObj is a difficult as
>>> dropping one file somewhere on your path I never got round to doing
>>> that. I only uploaded the 2.4 eggs to stop the turbogears folk crying. ;-)
>>>       
>> if that's the case then let me cry for 2.5 eggs too :D
>>     
>
> Seconded (or re-seconded? since I was the original poster). I first
> noticed the missing 2.5 eggs problem because of
> http://docs.turbogears.org/1.0/Python2.5Support too. I'd really like
> to see TurboGears with complete 2.5 ability, and that means bringing
> ConfigObj up to speed.
>
> Pretty please? :-)
>
>   
Ok, I'll look at getting a new release with 2.5 support and Nicola's new 
features done over the weekend.

Michael

Re: [Configobj-develop] Can't easy_install ConfigObj for Python 2.5

[Michael F. <fuz...@vo...>]

Robin Munn wrote:
> On 2/1/07, Jorge Vargas <jor...@gm...> wrote:
>   
>>> As for eggs... well seeing that installing ConfigObj is a difficult as
>>> dropping one file somewhere on your path I never got round to doing
>>> that. I only uploaded the 2.4 eggs to stop the turbogears folk crying. ;-)
>>>       
>> if that's the case then let me cry for 2.5 eggs too :D
>>     
>
> Seconded (or re-seconded? since I was the original poster). I first
> noticed the missing 2.5 eggs problem because of
> http://docs.turbogears.org/1.0/Python2.5Support too. I'd really like
> to see TurboGears with complete 2.5 ability, and that means bringing
> ConfigObj up to speed.
>
> Pretty please? :-)
>
>   
Ok, I'll look at getting a new release with 2.5 support and Nicola's new 
features done over the weekend.

Michael