Skip Menu |
 

This queue is for tickets about the JSON CPAN distribution.

Report information
The Basics
Id: 100423
Status: new
Priority: 0/
Queue: JSON

People
Owner: Nobody in particular
Requestors: avar [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 2.90
Fixed in: (no value)



Subject: Please remove the experimental -convert_blessed_universally option
MIME-Version: 1.0
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
Message-ID: <rt-4.0.18-23544-1416308761-1311.0-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 583
Download (untitled) / with headers
text/plain 583b
We hit an issue in production here at work where something stopped working because of the maxdepth problem described in RT #69620. This whole feature is just crazy IMO, nothing should be inserting stuff into UNIVERSAL at a distance like this, it means that loading random code that uses this -convert_blessed_universally option will screw with everything *globally*. We weren't even using JSON.pm in the code that broke, we were using JSON::XS. Please just remove this, it's not all that useful compared to just specifying options explicitly, and causes weird action at a distance.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.