# warning about old stuff in version 5.3 and 5.4
**URL:** https://discourse.paraview.org/t/warning-about-old-stuff-in-version-5-3-and-5-4/2531
**Category:** Development
**Created:** [September 10, 2019, 9:30am UTC](https://discourse.paraview.org/t/warning-about-old-stuff-in-version-5-3-and-5-4/2531 "2019-09-10T09:30:10Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@jfavre](https://discourse.paraview.org/u/jfavre)
#### Post date: [September 10, 2019, 9:30am UTC](https://discourse.paraview.org/t/warning-about-old-stuff-in-version-5-3-and-5-4/2531/1 "2019-09-10T09:30:10Z")
Hello all
I am using 5.7-RC3 and am still getting warnings as shown below, when running pvbatch. I am not using that PLY reader in my script, so I do not know where this comes from.
```
( 14.284s) [main thread] vtkSMProxy.cxx:886 WARN| vtkSMSourceProxy (0x35656c0): Proxy (sources, plyreader) has been de
precated in ParaView 5.3 and will be removed by ParaView 5.4.
This has been replaced by "PLYReader" which also supports a series of PLY files.
```
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [September 10, 2019, 9:38am UTC](https://discourse.paraview.org/t/warning-about-old-stuff-in-version-5-3-and-5-4/2531/2 "2019-09-10T09:38:09Z")
the plyreader has indeed not been removed yet, but is not used anywhere in ParaView.
Can you try to reproduce with `-dr` ?
---
### Author:  [@jfavre](https://discourse.paraview.org/u/jfavre)
#### Post date: [September 10, 2019, 1:27pm UTC](https://discourse.paraview.org/t/warning-about-old-stuff-in-version-5-3-and-5-4/2531/3 "2019-09-10T13:27:16Z")
The -dr option has no effect. Note that my $HOME/.config/ParaView folder has no ParaView5\*ini files at all. I am puzzled as to where this message would be triggered
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [September 10, 2019, 2:46pm UTC](https://discourse.paraview.org/t/warning-about-old-stuff-in-version-5-3-and-5-4/2531/4 "2019-09-10T14:46:01Z")
Do you have any ParaView version information set in your pvbatch scripts? E.g.,
```auto
paraview.compatibility.major = 5
paraview.compatibility.minor = 2
```
?
---
### Author:  [@jfavre](https://discourse.paraview.org/u/jfavre)
#### Post date: [September 10, 2019, 5:55pm UTC](https://discourse.paraview.org/t/warning-about-old-stuff-in-version-5-3-and-5-4/2531/5 "2019-09-10T17:55:49Z")
No, I have no python code with compatibility flag…
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [September 11, 2019, 3:09am UTC](https://discourse.paraview.org/t/warning-about-old-stuff-in-version-5-3-and-5-4/2531/6 "2019-09-11T03:09:46Z")
Could you share a simple script that reproduce the issue ?
---
### Author:  [@nicolas.vuaille](https://discourse.paraview.org/u/nicolas.vuaille)
#### Post date: [October 2, 2019, 10:00am UTC](https://discourse.paraview.org/t/warning-about-old-stuff-in-version-5-3-and-5-4/2531/7 "2019-10-02T10:00:55Z")
I reproduce in pvpython (built from 5.7 tag, also tested with master) with the following.
```python
from paraview.simple import *
LoadState("statefile.pvsm")
SetActiveView(GetRenderView())
```
For the state file, I simply ran ParaView with `./bin/paraview -dr` and immediately save the state.
[empty\_dr.pvsm](https://discourse.paraview.org/uploads/short-url/7voudCiZVaa5g55yoPcRP7IW1Qi.pvsm) (52.8 KB)