1.4.4 version released on Apr 25 is missing whl

[awaizman1]

Hi,

On Apr 25 a new 1.4 version (1.4.4) released to PyPi (although can't see this version in changelog).
This version, as opposed to other versions is released only as a source distribution and missing whl files.

This breaks all builds that depends on lazy-object-proxy using local organization pypi proxy with SSL connection due to pip bug pypa/pip#8999 (see details below)

Would you please release also whl files?

Details:
In my organization we configure pip to connect to local index-url with SSL certificate, this prevents pip accessing external repos during our CI. The local repo is also a proxy of pypi.
some of our projects depends on lazy-object-proxy 1.4.* - since 1.4.4 is the latest 1.4.x one and released as source dist, pip downloads the tar and tries to install it. When installing lazy-object-proxy it first tries to install its build dependencies (PEP517 I guess) so pip invokes itself again (lets call it sub-pip) to download build requirements.
Due to a bug in pip, the sub-pip gets the index-url but not the certificate argument, thus failing to validate the certificate against the local repo and all build fails.

Thanks

[ionelmc]

Aw hell - it was supposed to be a workaround for #51

I'll have to yank the 1.4.4 release @andy-maier - I now believe the proper fix for you is to take this code: https://github.com/ionelmc/python-lazy-object-proxy/releases/tag/v1.4.4 and republish it with a different name (lazy-andy-proxy or lazy-object-proxy-andry or whatever) 😐

[ionelmc]

1.4.4 is yanked now. Note that it's still installable - @andy-maier lemme know how this works.

If this ain't enough I'll delete it.

[ionelmc]

https://www.python.org/dev/peps/pep-0592/ for "yank"-ing details.

[awaizman1]

Thanks,

will appreciate if you can delete it for now since Nexus repo (and maybe others like Antifactory) doesn't mirror the 'yanked' attribute. https://issues.sonatype.org/browse/NEXUS-25231?jql=project%20%3D%20NEXUS%20AND%20component%20%3D%20PyPi

[ionelmc]

Deleted now.

[awaizman1]

Thanks a lot! all working now. sorry for bothering you.

[andy-maier]

@ionelmc Just wanted to provide a late response to your question above: We can live with that by not running pylint on Python 3.5, which is acceptable on such an old and meanwhile unsupported Python version. Sorry for causing the extra work for you.