Same here, but i normally do not follow them to the letter.I will usually add to them.
One of the main reasons i like to mimic Photo-Shop tutorials.This greatly enhances your gimp know how, because you often end up using some means of duplicating something in Photo-Shop that isn't in Gimps program.
You can learn a lot about Gimps hidden treasures that way.

WARNING: Plug-In "slinky-0.2.py"
(C:\Program Files\gimp-2.7.2\lib\gimp\2.0\plug-ins\slinky-0.2.py)
called deprecated procedure 'gimp-image-add-vectors'.
It should call 'gimp-image-insert-vectors' instead!

Got this error while running in 2.7, thanks for the help.

I think it still worked though

Yes in the 2.7 version of python the add command has been replaced with insert instead.
It will be up to all the developers of the python script plug-ins to update their scripts - most
probably will when 2.8 is released.
Many of the python files for 2.6 will give you this error.Most will still run though.
LayerFX will not even start - not for me anyways.

That sucks, speaking of scripts that need an update, could someone update the rain script by Fence Post?
Script

I hope (to the extreme) that the GIMP developers incorporate Python directly as part of the 2.8 install for Windows Users. Also, hope someone comes up with a translator/convertor for current python scripts to be acceptable to 2.8 standards. I can wish can't I? lol

Well then, time to start sending rain twords Partha and Photocomix? For that translator sounds really useful

I am going to venture to say the developers will not include the Python modules in Gimp-2.8 for Windows due to size.
This is why the help package isn't currently included. But if you download and install Python 2.7 you may be all set when the 2.8 version is released.I had it installed before i grabbed Parthas 2.7.2 version and it (Gimp-2.7.2) recognized Python 2.7 right away.

No ...not from the developers they do no provide binary or installers

Anyway the gimp 2.7.2 Windows build include support for Python out of the box ,
so obviously may be done .

If would be done by the Official Unofficial responsable of the windows builds, that is another question

But for sure a (also)portable gimp with python included would be a success

In most cases, Script and plug-in authors should NOT update their code to use the newer names of PDB functions. Doing so will prevent their code from working with the current (to be previous) version of GIMP. Unless you are exploiting new capabilities (layer groups, added text capabilities, etc), you should just continue to use the original name.

The deprecation warnings are just that, warnings. They are not necessarily errors which will interrupt the program. They are intended mainly for GIMP developers (such warnings are disabled in the stable releases) and for the scripts/plug-ins that ship with GIMP where there is no reason for them to run on previous versions (earlier GIMPs ship with their own set of such scripts/plug-ins).

The particular PDB function Willy's report addressed ('gimp-image-insert-vectors') is an enhancement intended to eventually support "path groups" in a manner that "layer groups" support is being added. Such support will not exist in GIMP 2.8! There is no functional reason to update a script using 'gimp-image-add-vectors' so that it uses the new function -- all this will accomplish is to break the script for GIMP 2.6 and earlier.

There is a similar situation with some of the 'gimp-drawable-*' procedures; GIMP 2.8 will rename many of them to 'gimp-item-*' ('gimp-item-width', 'gimp-item-get-name', etc). "Items" comprise both drawables and layer groups. Unless your script/plug-in is actually going to do something with layer groups, you should probably stick with the 'gimp-drawable-*' procedures so it works with both 2.6 and 2.8 (if your scripts need to handle layer groups or you don't care about backwards compatibility then you can use the 'gimp-item-*' procedure).

Unless you are creating a script to make use of the new functionality, the time to update your scripts/plug-ins will be after most people have switched to using GIMP 2.8 and only the few people still using 2.6 will be affected by your update. It is usually better to wait as long as possible before updating your scripts. This way you won't have to maintain separate versions and you will minimize complaints from users who use the wrong version.

Thanks for clearing that up for us Saulgoode.