On 05/12/2019 12:45 pm, Karthikeyan wrote:
> On Thu, Dec 5, 2019, 5:53 PM Mark Shannon <mark@hotpy.org
> <mailto:mark@hotpy.org>> wrote:
>
>
>
> On 04/12/2019 2:31 am, Gregory P. Smith wrote:
> >
> >
> > On Tue, Dec 3, 2019 at 8:21 AM Mark Shannon <mark@hotpy.org
> <mailto:mark@hotpy.org>
> > <mailto:mark@hotpy.org <mailto:mark@hotpy.org>>> wrote:
> >
> > Hi Everyone,
> >
> > I am proposing a new PEP, still in draft form, to impose a
> limit of one
> > million on various aspects of Python programs, such as the
> lines of
> > code
> > per module.
> >
> > Any thoughts or feedback?
> >
>
> [snip]
>
> >
> >
> > Overall I /like/ the idea of limits... /But.../ in my experience,
> limits
> > like this tend to impact generated source code or generated
> bytecode,
> > and thus any program that transitively uses those.
> >
> > Hard limits within the Javaish world have been *a major pain* on the
> > Android platform for example. I wouldn't call workarounds
> > straightforward when it comes to total number of classes or
> methods in a
> > process.
>
> Do you have any numbers? 1M is a lot bigger then 64K, but real world
> numbers would be helpful.
>
>
> I guess the relevant case in question is with Facebook patching the
> limit of 65,000 classes in Android :
> https://m.facebook.com/notes/facebook-engineering/under-the-hood-dalvik-patch-for-facebook-for-android/10151345597798920
Is that the correct link? That seems to be an issue with an internal
buffer size, not the limit on the number of classes.
>
> >
> > If we're to adopt limits where there were previously none, we
> need to do
> > it via a multi-release deprecation cycle feedback loop to give
> people a
> > way to find report use cases that exceed the limits in real world
> > practical applications. So the limits can be reconsidered or the
> > recommended workarounds tested and agreed upon.
> >
> > -gps
> _______________________________________________
> Python-Dev mailing list -- python-dev@python.org
> <mailto:python-dev@python.org>
> To unsubscribe send an email to python-dev-leave@python.org
> <mailto:python-dev-leave@python.org>
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-dev@python.org/message/ECKES7IPWGD74DAKFYV7JEWNOBAFEWYF/
> Code of Conduct: http://python.org/psf/codeofconduct/
>