Arrrrgh! Another module broken

Jive Dadson

unread,

Jan 17, 2010, 8:25:39 PM1/17/10

to

I just found another module that broke when I went to 2.6. Gnuplot.
Apparently one of its routines has a parameter named "with." That used
to be okay, and now it's not.

Once I get everything to work under 2.6, I am using it forever or until
new releases no longer break working code, whichever comes first.

Chris Rebert

unread,

Jan 17, 2010, 9:02:40 PM1/17/10

to pytho...@python.org

The latter ain't gonna happen. Going 2.x --> 3.x *will* break code,
and no future 3.x version will change that fact.

Cheers,
Chris
--
http://blog.rebertia.com

Matt Newville

unread,

Jan 17, 2010, 9:21:35 PM1/17/10

to

On Jan 17, 7:25 pm, Jive Dadson <notonthe...@noisp.com> wrote:
> I just found another module that broke when I went to 2.6. > Gnuplot. Apparently one of its routines has a parameter
> named "with." That used to be okay, and now it's not.

This was fixed in version 1.8 of Gnuplot.py

> Once I get everything to work under 2.6, I am using it
> forever or until new releases no longer break working
> code, whichever comes first.

Hey, good luck with that forever plan.

--Matt

Jive Dadson

unread,

Jan 17, 2010, 9:33:17 PM1/17/10

to

Matt Newville wrote:
> Hey, good luck with that forever plan.
>
> --Matt

Yeah, I know. I'm just glad I don't have to get new executables and
dll's from all my software vendors every Tuesday when the MS Window XP
updates come out.

2.6 FOREVER!

Jive Dadson

unread,

Jan 17, 2010, 9:51:43 PM1/17/10

to

Thanks. I also had to install a new version of numpy. Have I kvetched
enough about have to track down new versions of all my third party stuff
every time I up-rev Python? I guess so. :-)

2.6 FOREVER!

Jive Dadson

unread,

Jan 18, 2010, 12:44:44 AM1/18/10

to

I have source code that uses the "with" kwarg. What do I replace it with?

Chris Rebert

unread,

Jan 18, 2010, 12:55:36 AM1/18/10

to Jive Dadson, pytho...@python.org

On Sun, Jan 17, 2010 at 9:44 PM, Jive Dadson <noton...@noisp.com> wrote:
> Matt Newville wrote:
>>
>> On Jan 17, 7:25 pm, Jive Dadson <notonthe...@noisp.com> wrote:
>>>
>>> I just found another module that broke when I went to 2.6. > Gnuplot.
>>> Apparently one of its routines has a parameter
>>> named "with." That used to be okay, and now it's not.
>>
>> This was fixed in version 1.8 of Gnuplot.py
>>
>>> Once I get everything to work under 2.6, I am using it
>>> forever or until new releases no longer break working
>>> code, whichever comes first.
>>
>> Hey, good luck with that forever plan.
>

> I have source code that uses the "with" kwarg. What do I replace it with?

Rename the argument to something else that's not a Python keyword.
When keyword conflicts occur, appending an underscore (i.e. with_) is
a popular option, as is using a nonstandard spelling (e.g. wif)

r0g

unread,

Jan 18, 2010, 12:57:18 AM1/18/10

to

Good old fashioned open() and close()

Roger.

Jive Dadson

unread,

Jan 18, 2010, 2:11:38 AM1/18/10

to

I found the answer. The new kwarg in Gnuplot is "with_".

Grant Edwards

unread,

Jan 18, 2010, 11:37:22 AM1/18/10

to

On 2010-01-18, Jive Dadson <noton...@noisp.com> wrote:
> I just found another module that broke when I went to 2.6. Gnuplot.
> Apparently one of its routines has a parameter named "with." That used
> to be okay, and now it's not.

I remember seeing depreicated warnings about that _years_ ago,
and I would have sworn it's been fixed for at least a couple
years.

--
Grant

nn

unread,

Jan 19, 2010, 11:44:12 AM1/19/10

to

On Jan 18, 11:37 am, Grant Edwards <inva...@invalid.invalid> wrote:

FWIW, "with" deprecation warnings exist since September 19, 2006 when
Python 2.5 was released.