pypi / support Goto Github PK

I'd like to take ownership over the PyPI project name it so that i can publish my IT (InspectorTiger) project under that name. It is inactive for years and there is no given homepage / github repo.

I believe this falls under the "Invalid project" case described in PEP541.

I mailed the author @gregoil but no response in 24+ hours.

Hi, my understanding is that if we believe that a project is abandoned by the rules of PEP 541, the current process is to post an issue here, since there is no other process at pypi.org. If that's wrong, please let me know and I'll close this.

I believe that django-rest-scaffold is abandoned and I would like to use that name for a project. The package hasn't been updated in over 3 years and only has pre-releases.

• the project has been determined abandoned by the rules described above;
  • owner not reachable (see Reachability above);
  • no releases within the past twelve months; and
  • no activity from the owner on the project's home page (or no home page listed).

The only one that I'm not sure about is reachability because PEP 541 says that the Package Index maintainers must attempt to reach the user. I've emailed them and opened an issue on GitHub, and I considered waiting longer, but because of the wording on PEP 541, it sounds like I'm supposed to request the Index maintainers to do that. They may not take my forwarded email as "proof".

• the candidate is able to demonstrate their own failed attempts to contact the existing owner;

I can post my email (though I wouldn't consider that 'proof') and I did open an issue on their GitHub asking if the project is abandoned.

• the candidate is able to demonstrate that the project suggested to reuse the name already exists and meets notability requirements;

My project is at https://github.com/gregschmit/django-rest-scaffold, but the current project isn't "notable" as far as I can tell. The latest release is 0.0.1a8 and my version will start at 0.1, so it will be clear that this is a new pre-release, and this abides by SemVer:

Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.

• the candidate is able to demonstrate why a fork under a different name is not an acceptable workaround;

The current project is in pre-release and I will leave the old versions up to ensure that nothing breaks for current users.

• download statistics on the Package Index for the existing package indicate project is not being used; and

The downloads seem to be in line with projects that are unusable, so I have no indication that organic downloads from real users are happening. Either way, I would keep the old version to ensure nothing breaks and to keep consistency in the index.

• the maintainers of the Package Index don't have any additional reservations.

Can anyone provide feedback to see if if I could be added as the owner of the django-rest-scaffold PyPi project?

I'd like to request that the phantom project on PyPI be transferred to PyPI user bconstanzo.

The phantom project was registered in 9 Sep 2019 by user "eaybek ", along with other ~30 projects that are namesquatting. In particular, I was waiting to upload to PyPI my own phantom project, and I found today that 14 days ago the name was taken and the repo it links to is barely a skeleton of a project to keep the name: https://github.com/eaybek/phantom/ (which is nearly empty). He even says so in the description of the package:

phantom reserved for self usage purpose

(see https://pypi.org/project/phantom/ and attached screenshot)

I was waiting for a more proper time to upload phantom (https://github.com/bconstanzo/phantom) but I found out today the name had been squatted with basically an empty shell of a project just to "reserve the name".

As I said, this is not the only case where the user is namesquatting, most of the 35 projects eaybek has uploaded to pypi simply occupy a name. The repos linked contain very basic structure to comply with pypi requirements, but the code does nothing in particular, see for example:

• may: https://github.com/eaybek/may/blob/master/may/may.py
• could: https://github.com/eaybek/could/blob/master/could/could.py
• fastpress: https://github.com/eaybek/fastpress/ (this one barely has files with content in them)

And this pattern is repetead for almost all of his PyPI packages.

I believe the https://pypi.org/project/texteditor/ is an invalid project:

• The content is a copy-pasted Python exercise with an absolute minimal setup.py, no README and a misspelled license.
• It was uploaded a year and a half ago (September 2017) and hasn't been touch since.
• The linked homepage returns a 404.
• The repo is a mix of other copy-pasted Python exercises.
• Nobody answer at the listed email.

In fact, I suspect that the user is a fake account, but that's beyond this issue.

Disclaimer: I own the project text-editor (with a dash) so I'm worried about name confusion.

The sphinxcontrib-domaintools package on PyPI is backed by https://github.com/sphinx-contrib/domaintools, for which @klorenz and @tk0miya have commit rights.

The package no longer works with recent python3 or pip, and while there are PRs to fix those problems, the only PyPI maintainer, @klorenz, is unfortunately not responsive. @tk0miya points out that while they can merge the PRs, they would not have the ability to publish to PyPI.

The easiest way out of this situation would be to add @tk0miya as a maintainer on PyPI. I'll let @tk0miya confirm that this is desirable. I haven't successfully made contact with @klorenz when asking this question.

Hi, I work for the @Telecominfraproject organization as a maintainer of the oopt-gnpy software. Previously, this stuff was done by James Powell (@dutc) who also created the gnpy package at pypi. James is no longer with @Telecominfraproject, unfortunately, meaning that the maintainer address listed in PyPI's Meta -> Author no longer works.

Can you please pass the ownership of gnpy to my account jktjkt?

I was not able to secure a proper handover before James' mail account was closed. I'm sorry that our internal process flaw causes extra work for you. I'll make sure that this event does not repeat by ensuring that there are more accounts distributed among several companies which are all listed as co-maintainers.

refs Telecominfraproject/oopt-gnpy#254

Request

I'd like to transfer the ownership of the abandoned pynq package (PyPI) to myself (PyPI account and GitHub repository). The last release of the current PYPI project was 10 years ago in 2009. The current PYPI pynq-package's project homepage is now owned by a unrelated meetup group.

Rationale

The package is abandoned

The last release of the project was 10 years ago in 2009. The homepage points to unrelated content.

Our 'pynq' has a growing community

We are hosted on github now and have over 700 stars. Many projects depend on us, but don't have a way to cleanly pip install pynq directly. Our project is unrelated to the current PYPI pynq package.

I have contacted the previous owner twice over the past 3 weeks with no response.

Referencing and one more ping to @heynemann, the current owner of the PYPI pynq package.

My Platform

Network telemetry

DNS Resolution

dig pypi.org A
<'dig' is not recognized as an internal or external command,
operable program or batch file.>    same for all related 'dig' tests

dig pypi.org AAAA
<Replace with your output>

dig files.pythonhosted.org A
<Replace with your output>

dig files.pythonhosted.org AAAA
<Replace with your output>

Traceroutes

IPv4

traceroute pypi.org
<'traceroute' is not recognized as an internal or external command,
operable program or batch file.>  same for all other tests using 'traceroute'

traceroute files.pythonhosted.org
<Replace with your output>

IPv6 (If available)

traceroute6 pypi.org
<Replace with your output>

traceroute6 files.pythonhosted.org
<Replace with your output>

HTTPS Requests

IPv4

curl -vvv -I --ipv4 https://pypi.org/pypi/pip/json
<*   Trying 151.101.64.223...
* TCP_NODELAY set
* Connected to pypi.org (151.101.64.223) port 443 (#0)
* schannel: SSL/TLS connection with pypi.org port 443 (step 1/3)
* schannel: checking server certificate revocation
* schannel: sending initial handshake data: sending 173 bytes...
* schannel: sent initial handshake data: sent 173 bytes
* schannel: SSL/TLS connection with pypi.org port 443 (step 2/3)
* schannel: failed to receive handshake, need more data
* schannel: SSL/TLS connection with pypi.org port 443 (step 2/3)
* schannel: encrypted data got 4096
* schannel: encrypted data buffer: offset 4096 length 4096
* schannel: encrypted data length: 139
* schannel: encrypted data buffer: offset 139 length 4096
* schannel: received incomplete message, need more data
* schannel: SSL/TLS connection with pypi.org port 443 (step 2/3)
* schannel: encrypted data got 175
* schannel: encrypted data buffer: offset 314 length 4096
* schannel: sending next handshake data: sending 93 bytes...
* schannel: SSL/TLS connection with pypi.org port 443 (step 2/3)
* schannel: encrypted data got 242
* schannel: encrypted data buffer: offset 242 length 4096
* schannel: SSL/TLS handshake complete
* schannel: SSL/TLS connection with pypi.org port 443 (step 3/3)
* schannel: stored credential handle in session cache
> HEAD /pypi/pip/json HTTP/1.1
> Host: pypi.org
> User-Agent: curl/7.55.1
> Accept: */*
>
* schannel: client wants to read 102400 bytes
* schannel: encdata_buffer resized 103424
* schannel: encrypted data buffer: offset 0 length 103424
* schannel: encrypted data got 1573
* schannel: encrypted data buffer: offset 1573 length 103424
* schannel: decrypted data length: 1544
* schannel: decrypted data added: 1544
* schannel: decrypted data cached: offset 1544 length 102400
* schannel: encrypted data buffer: offset 0 length 103424
* schannel: decrypted data buffer: offset 1544 length 102400
* schannel: schannel_recv cleanup
* schannel: decrypted data returned 1544
* schannel: decrypted data buffer: offset 0 length 102400
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Access-Control-Allow-Headers: Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since
Access-Control-Allow-Headers: Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since
< Access-Control-Allow-Methods: GET
Access-Control-Allow-Methods: GET
< Access-Control-Allow-Origin: *
Access-Control-Allow-Origin: *
< Access-Control-Expose-Headers: X-PyPI-Last-Serial
Access-Control-Expose-Headers: X-PyPI-Last-Serial
< Access-Control-Max-Age: 86400
Access-Control-Max-Age: 86400
< Cache-Control: max-age=900, public
Cache-Control: max-age=900, public
< Content-Security-Policy: base-uri 'self'; block-all-mixed-content; connect-src 'self' https://api.github.com/repos/ *.fastly-insights.com sentry.io https://2p66nmmycsj3.statuspage.io; default-src 'none'; font-src 'self' fonts.gstatic.com; form-action 'self'; frame-ancestors 'none'; frame-src 'none'; img-src 'self' https://warehouse-camo.cmh1.psfhosted.org/ www.google-analytics.com *.fastly-insights.com; script-src 'self' www.googletagmanager.com www.google-analytics.com *.fastly-insights.com https://cdn.ravenjs.com; style-src 'self' fonts.googleapis.com; worker-src *.fastly-insights.com
Content-Security-Policy: base-uri 'self'; block-all-mixed-content; connect-src 'self' https://api.github.com/repos/ *.fastly-insights.com sentry.io https://2p66nmmycsj3.statuspage.io; default-src 'none'; font-src 'self' fonts.gstatic.com; form-action 'self'; frame-ancestors 'none'; frame-src 'none'; img-src 'self' https://warehouse-camo.cmh1.psfhosted.org/ www.google-analytics.com *.fastly-insights.com; script-src 'self' www.googletagmanager.com www.google-analytics.com *.fastly-insights.com https://cdn.ravenjs.com; style-src 'self' fonts.googleapis.com; worker-src *.fastly-insights.com
< Content-Type: application/json
Content-Type: application/json
< ETag: "NpNAeA1vNqshUWwJGJ3nYA"
ETag: "NpNAeA1vNqshUWwJGJ3nYA"
< Referrer-Policy: origin-when-cross-origin
Referrer-Policy: origin-when-cross-origin
< Server: nginx/1.13.9
Server: nginx/1.13.9
< X-PyPI-Last-Serial: 5725987
X-PyPI-Last-Serial: 5725987
< Content-Length: 75584
Content-Length: 75584
< Accept-Ranges: bytes
Accept-Ranges: bytes
< Date: Mon, 02 Sep 2019 18:19:50 GMT
Date: Mon, 02 Sep 2019 18:19:50 GMT
< Connection: keep-alive
Connection: keep-alive
< X-Served-By: cache-iad2129-IAD, cache-mdw17370-MDW
X-Served-By: cache-iad2129-IAD, cache-mdw17370-MDW
< X-Cache: MISS, HIT
X-Cache: MISS, HIT
< X-Cache-Hits: 0, 2
X-Cache-Hits: 0, 2
< X-Timer: S1567448391.539876,VS0,VE0
X-Timer: S1567448391.539876,VS0,VE0
< Vary: Accept-Encoding, Accept-Encoding
Vary: Accept-Encoding, Accept-Encoding
< Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
< X-Frame-Options: deny
X-Frame-Options: deny
< X-XSS-Protection: 1; mode=block
X-XSS-Protection: 1; mode=block
< X-Content-Type-Options: nosniff
X-Content-Type-Options: nosniff
< X-Permitted-Cross-Domain-Policies: none
X-Permitted-Cross-Domain-Policies: none

<
* Connection #0 to host pypi.org left intact>

curl -vvv -I --ipv4 https://files.pythonhosted.org/packages/ae/e8/2340d46ecadb1692a1e455f13f75e596d4eab3d11a57446f08259dee8f02/pip-10.0.1.tar.gz
<*   Trying 199.232.37.63...
* TCP_NODELAY set
* Connected to files.pythonhosted.org (199.232.37.63) port 443 (#0)
* schannel: SSL/TLS connection with files.pythonhosted.org port 443 (step 1/3)
* schannel: checking server certificate revocation
* schannel: sending initial handshake data: sending 187 bytes...
* schannel: sent initial handshake data: sent 187 bytes
* schannel: SSL/TLS connection with files.pythonhosted.org port 443 (step 2/3)
* schannel: failed to receive handshake, need more data
* schannel: SSL/TLS connection with files.pythonhosted.org port 443 (step 2/3)
* schannel: encrypted data got 4096
* schannel: encrypted data buffer: offset 4096 length 4096
* schannel: encrypted data length: 256
* schannel: encrypted data buffer: offset 256 length 4096
* schannel: received incomplete message, need more data
* schannel: SSL/TLS connection with files.pythonhosted.org port 443 (step 2/3)
* schannel: encrypted data got 1614
* schannel: encrypted data buffer: offset 1870 length 4096
* schannel: sending next handshake data: sending 93 bytes...
* schannel: SSL/TLS connection with files.pythonhosted.org port 443 (step 2/3)
* schannel: encrypted data got 258
* schannel: encrypted data buffer: offset 258 length 4096
* schannel: SSL/TLS handshake complete
* schannel: SSL/TLS connection with files.pythonhosted.org port 443 (step 3/3)
* schannel: stored credential handle in session cache
> HEAD /packages/ae/e8/2340d46ecadb1692a1e455f13f75e596d4eab3d11a57446f08259dee8f02/pip-10.0.1.tar.gz HTTP/1.1
> Host: files.pythonhosted.org
> User-Agent: curl/7.55.1
> Accept: */*
>
* schannel: client wants to read 102400 bytes
* schannel: encdata_buffer resized 103424
* schannel: encrypted data buffer: offset 0 length 103424
* schannel: encrypted data got 899
* schannel: encrypted data buffer: offset 899 length 103424
* schannel: decrypted data length: 870
* schannel: decrypted data added: 870
* schannel: decrypted data cached: offset 870 length 102400
* schannel: encrypted data buffer: offset 0 length 103424
* schannel: decrypted data buffer: offset 870 length 102400
* schannel: schannel_recv cleanup
* schannel: decrypted data returned 870
* schannel: decrypted data buffer: offset 0 length 102400
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Connection: keep-alive
Connection: keep-alive
< Content-Length: 1246072
Content-Length: 1246072
< x-amz-id-2: MNR5NHajB8o+49KirEEIz2DJ5GwZyCPFHm6rq+Oq2JfvvuU8jQhq3LtWfSkku4NSAG0G7zqgTDs=
x-amz-id-2: MNR5NHajB8o+49KirEEIz2DJ5GwZyCPFHm6rq+Oq2JfvvuU8jQhq3LtWfSkku4NSAG0G7zqgTDs=
< x-amz-request-id: 6635E682C4887BE6
x-amz-request-id: 6635E682C4887BE6
< Last-Modified: Thu, 19 Apr 2018 18:56:10 GMT
Last-Modified: Thu, 19 Apr 2018 18:56:10 GMT
< ETag: "83a177756e2c801d0b3a6f7b0d4f3f7e"
ETag: "83a177756e2c801d0b3a6f7b0d4f3f7e"
< x-amz-version-id: 1N.JvpbFmUQle7Hn0tnUuxQqUTsn5iEu
x-amz-version-id: 1N.JvpbFmUQle7Hn0tnUuxQqUTsn5iEu
< Content-Type: binary/octet-stream
Content-Type: binary/octet-stream
< Server: AmazonS3
Server: AmazonS3
< Cache-Control: max-age=365000000, immutable, public
Cache-Control: max-age=365000000, immutable, public
< Accept-Ranges: bytes
Accept-Ranges: bytes
< Date: Mon, 02 Sep 2019 18:18:57 GMT
Date: Mon, 02 Sep 2019 18:18:57 GMT
< Age: 419099
Age: 419099
< X-Served-By: cache-sea1036-SEA, cache-lga21936-LGA
X-Served-By: cache-sea1036-SEA, cache-lga21936-LGA
< X-Cache: HIT, HIT
X-Cache: HIT, HIT
< X-Cache-Hits: 1, 1
X-Cache-Hits: 1, 1
< X-Timer: S1567448338.734245,VS0,VE31
X-Timer: S1567448338.734245,VS0,VE31
< Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
< X-Frame-Options: deny
X-Frame-Options: deny
< X-XSS-Protection: 1; mode=block
X-XSS-Protection: 1; mode=block
< X-Content-Type-Options: nosniff
X-Content-Type-Options: nosniff
< X-Permitted-Cross-Domain-Policies: none
X-Permitted-Cross-Domain-Policies: none
< X-Robots-Header: noindex
X-Robots-Header: noindex

<
* Connection #0 to host files.pythonhosted.org left intact>

IPv6 (If available)

curl -vvv -I --ipv6 https://pypi.org/pypi/pip/json
<*   Trying 151.101.0.223...
* TCP_NODELAY set
* Connected to pypi.org (151.101.0.223) port 443 (#0)
* schannel: SSL/TLS connection with pypi.org port 443 (step 1/3)
* schannel: checking server certificate revocation
* schannel: sending initial handshake data: sending 173 bytes...
* schannel: sent initial handshake data: sent 173 bytes
* schannel: SSL/TLS connection with pypi.org port 443 (step 2/3)
* schannel: failed to receive handshake, need more data
* schannel: SSL/TLS connection with pypi.org port 443 (step 2/3)
* schannel: encrypted data got 4096
* schannel: encrypted data buffer: offset 4096 length 4096
* schannel: encrypted data length: 139
* schannel: encrypted data buffer: offset 139 length 4096
* schannel: received incomplete message, need more data
* schannel: SSL/TLS connection with pypi.org port 443 (step 2/3)
* schannel: encrypted data got 175
* schannel: encrypted data buffer: offset 314 length 4096
* schannel: sending next handshake data: sending 93 bytes...
* schannel: SSL/TLS connection with pypi.org port 443 (step 2/3)
* schannel: encrypted data got 242
* schannel: encrypted data buffer: offset 242 length 4096
* schannel: SSL/TLS handshake complete
* schannel: SSL/TLS connection with pypi.org port 443 (step 3/3)
* schannel: stored credential handle in session cache
> HEAD /pypi/pip/json HTTP/1.1
> Host: pypi.org
> User-Agent: curl/7.55.1
> Accept: */*
>
* schannel: client wants to read 102400 bytes
* schannel: encdata_buffer resized 103424
* schannel: encrypted data buffer: offset 0 length 103424
* schannel: encrypted data got 1573
* schannel: encrypted data buffer: offset 1573 length 103424
* schannel: decrypted data length: 1544
* schannel: decrypted data added: 1544
* schannel: decrypted data cached: offset 1544 length 102400
* schannel: encrypted data buffer: offset 0 length 103424
* schannel: decrypted data buffer: offset 1544 length 102400
* schannel: schannel_recv cleanup
* schannel: decrypted data returned 1544
* schannel: decrypted data buffer: offset 0 length 102400
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Access-Control-Allow-Headers: Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since
Access-Control-Allow-Headers: Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since
< Access-Control-Allow-Methods: GET
Access-Control-Allow-Methods: GET
< Access-Control-Allow-Origin: *
Access-Control-Allow-Origin: *
< Access-Control-Expose-Headers: X-PyPI-Last-Serial
Access-Control-Expose-Headers: X-PyPI-Last-Serial
< Access-Control-Max-Age: 86400
Access-Control-Max-Age: 86400
< Cache-Control: max-age=900, public
Cache-Control: max-age=900, public
< Content-Security-Policy: base-uri 'self'; block-all-mixed-content; connect-src 'self' https://api.github.com/repos/ *.fastly-insights.com sentry.io https://2p66nmmycsj3.statuspage.io; default-src 'none'; font-src 'self' fonts.gstatic.com; form-action 'self'; frame-ancestors 'none'; frame-src 'none'; img-src 'self' https://warehouse-camo.cmh1.psfhosted.org/ www.google-analytics.com *.fastly-insights.com; script-src 'self' www.googletagmanager.com www.google-analytics.com *.fastly-insights.com https://cdn.ravenjs.com; style-src 'self' fonts.googleapis.com; worker-src *.fastly-insights.com
Content-Security-Policy: base-uri 'self'; block-all-mixed-content; connect-src 'self' https://api.github.com/repos/ *.fastly-insights.com sentry.io https://2p66nmmycsj3.statuspage.io; default-src 'none'; font-src 'self' fonts.gstatic.com; form-action 'self'; frame-ancestors 'none'; frame-src 'none'; img-src 'self' https://warehouse-camo.cmh1.psfhosted.org/ www.google-analytics.com *.fastly-insights.com; script-src 'self' www.googletagmanager.com www.google-analytics.com *.fastly-insights.com https://cdn.ravenjs.com; style-src 'self' fonts.googleapis.com; worker-src *.fastly-insights.com
< Content-Type: application/json
Content-Type: application/json
< ETag: "NpNAeA1vNqshUWwJGJ3nYA"
ETag: "NpNAeA1vNqshUWwJGJ3nYA"
< Referrer-Policy: origin-when-cross-origin
Referrer-Policy: origin-when-cross-origin
< Server: nginx/1.13.9
Server: nginx/1.13.9
< X-PyPI-Last-Serial: 5725987
X-PyPI-Last-Serial: 5725987
< Content-Length: 75584
Content-Length: 75584
< Accept-Ranges: bytes
Accept-Ranges: bytes
< Date: Mon, 02 Sep 2019 18:15:47 GMT
Date: Mon, 02 Sep 2019 18:15:47 GMT
< Connection: keep-alive
Connection: keep-alive
< X-Served-By: cache-iad2129-IAD, cache-mdw17351-MDW
X-Served-By: cache-iad2129-IAD, cache-mdw17351-MDW
< X-Cache: MISS, HIT
X-Cache: MISS, HIT
< X-Cache-Hits: 0, 1
X-Cache-Hits: 0, 1
< X-Timer: S1567448148.874979,VS0,VE1
X-Timer: S1567448148.874979,VS0,VE1
< Vary: Accept-Encoding, Accept-Encoding
Vary: Accept-Encoding, Accept-Encoding
< Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
< X-Frame-Options: deny
X-Frame-Options: deny
< X-XSS-Protection: 1; mode=block
X-XSS-Protection: 1; mode=block
< X-Content-Type-Options: nosniff
X-Content-Type-Options: nosniff
< X-Permitted-Cross-Domain-Policies: none
X-Permitted-Cross-Domain-Policies: none

<
* Connection #0 to host pypi.org left intact>

curl -vvv -I --ipv6 https://files.pythonhosted.org/packages/ae/e8/2340d46ecadb1692a1e455f13f75e596d4eab3d11a57446f08259dee8f02/pip-10.0.1.tar.gz
<*   Trying 2a04:4e42:46::319...
* TCP_NODELAY set
* Connected to files.pythonhosted.org (2a04:4e42:46::319) port 443 (#0)
* schannel: SSL/TLS connection with files.pythonhosted.org port 443 (step 1/3)
* schannel: checking server certificate revocation
* schannel: sending initial handshake data: sending 187 bytes...
* schannel: sent initial handshake data: sent 187 bytes
* schannel: SSL/TLS connection with files.pythonhosted.org port 443 (step 2/3)
* schannel: failed to receive handshake, need more data
* schannel: SSL/TLS connection with files.pythonhosted.org port 443 (step 2/3)
* schannel: failed to receive handshake, SSL/TLS connection failed
* Closing connection 0
* schannel: shutting down SSL/TLS connection with files.pythonhosted.org port 443
* Send failure: Connection was reset
* schannel: failed to send close msg: Failed sending data to the peer (bytes written: -1)
* schannel: clear security context handle
curl: (35) schannel: failed to receive handshake, SSL/TLS connection failed>

TLS Debug

IPv4

echo -n | openssl s_client -4 -connect pypi.org:443
<'openssl' is not recognized as an internal or external command,
operable program or batch file.>

echo -n | openssl s_client -4 -connect files.pythonhosted.org:443
<Replace with your output>

IPv6 (If available)

echo -n | openssl s_client -6 -connect pypi.org:443
<Replace with your output>

echo -n | openssl s_client -6 -connect files.pythonhosted.org:443
<Replace with your output>

Harking back to pypi/warehouse#5196, there is a package which appears to be squatting and it too broken to install named 'grpc' registered at https://pypi.org/project/grpc/ . It hold the name the 'grpcio' package should hold.

Hi,
I'm testing package uploading to test.pypi.org using pip-analogj-test and it looks like I have previously created that project with another email address. When I attempted to reset the password for that email, test.pypi.org told me that the user or email address was not found.

Can you help me get that package transferred to the AnalogJ user on test.pypi.org? https://test.pypi.org/user/analogj/

Thanks!

Hi!

Seems I'm not the only one to run into this. #7 and pypi/warehouse#5503 had the same issue. I was able to successfully upload my project dirs to TestPyPI. I had selected the name based on it returning a 404 on PyPI proper. Turns out there must have been a project with that name in the past, as I can't upload my initial release.

This also blocks me from uploading a few other projects that use dirs as a dependency, so anything I can do to help speed along this process would help, as I believe I can't just upload packages that depend on git repositories in the meantime. 😉

I would rename this, but several other possible names are collisions and those projects are actually still being developed. If there's anything I can do to help speed this along please let me know.

Hi,

We would like to host the ROCm-enhanced version of TensorFlow on PyPI.

However, we hit the 60MB limit when trying to upload to test.pypi.org. In the meantime, we have created placeholder 0.0.1-versioned projects for tensorflow-rocm-enhanced on both Test PyPI and PyPI.

Details:

• Project name: tensorflow-rocm-enhanced
• PyPI links:
  • https://pypi.org/project/tensorflow-rocm-enhanced
  • https://test.pypi.org/project/tensorflow-rocm-enhanced
• Size: 189 MB per whl initially, but could eventually be more
• Indexes: both Test PyPI and PyPI

For some context, the builds for tensorflow derivatives tend to be reasonably large. For example, the tensorflow-gpu package is in the range of 100-200+ MB.

Please let us know how to move forward.

Best,

Jeff

edit:
CC'ing @sunway513

What's the problem this feature will solve?

HTTPError: 400 Client Error: File too large. Limit for project 'tensorflow-gcp' is 60 MB. See https://test.pypi.org/help/#file-size-limit for url: https://test.pypi.org/legacy/

Describe the solution you'd like
We need the limit to be increased to 200 MB

-rwxr-xr-x 1 root root 134179213 Jul 29 05:48 tensorflow-1.13.1-cp27-cp27mu-linux_x86_64.whl
-rwxr-xr-x 1 root root 134171914 Jul 29 05:48 tensorflow-1.13.1-cp35-cp35m-linux_x86_64.whl
-rwxr-xr-x 1 root root 134172064 Jul 29 05:48 tensorflow-1.13.1-cp36-cp36m-linux_x86_64.whl
-rwxr-xr-x 1 root root 146987529 Jul 11 00:38 tensorflow-1.14.0-cp27-cp27mu-linux_x86_64.whl
-rwxr-xr-x 1 root root 146975236 Jul 11 00:38 tensorflow-1.14.0-cp35-cp35m-linux_x86_64.whl
-rwxr-xr-x 1 root root 146975378 Jul 11 00:38 tensorflow-1.14.0-cp36-cp36m-linux_x86_64.whl
-rwxr-xr-x 1 root root 146974780 Jul 11 00:38 tensorflow-1.14.0-cp37-cp37m-linux_x86_64.whl

Projects:

https://test.pypi.org/manage/project/tensorflow-gcp/
https://pypi.org/project/tensorflow-gcp/

Module: https://pypi.org/project/Flask-Crud
Last release: 2014
Project description: UNKNOWN

I have opened a ticket on GitHub asking if I can take it over and sent an email to the author at [email protected]

Thanks!

I would like to request transfer of ownership of the project dokuwikixmlrpc to myself as per pypi/warehouse#1506.

I took over maintenance of this project in 2014 and the original author / previous maintainer @chimeric transferred the GitHub repository chimeric/dokuwikixmlrpc over to me in 2016. When you follow the "Homepage" link at https://pypi.org/project/dokuwikixmlrpc/ you will be redirected to the repository I maintain.

He does not have access to his PyPI account nor the email address associated with it any more and is therefore unable to do the transfer himself.

Just to be clear: this will be a continuation of the same project under a new maintainer and any existing releases can be kept as they are.

Below is an excerpt from an email exchange, which didn't go anywhere at the time since PyPI did not have a process for transfer of ownership:

From: Michael Klier <REDACTED>
Date: Mon, Sep 26, 2016 at 7:40 AM
Subject: Re: Maintenance of dokuvimki, dokuwikixmlrpc
To: Florian Rathgeber <REDACTED>

Hey Florian,

wow, cool to hear this stuff is still being used :)!

[...]

Re the PyPi - I would love to do that but unfortunately I don't remember the password
anymore and the mailserver I used to register has been down for years now. Not sure
if there's a way to recover that account. If you want to talk to the PyPi admins and explain
the situtation I'll be happy to help out as best as I can with providing relevant info etc..

Cheers,
Michael

On 25 September 2016 at 23:37, Florian Rathgeber <REDACTED> wrote:
>
> Hi Michael,
>
> Apologies for reviving a 2 year old email conversation: I'm in fact
> *still* using dokuvimki!
>
> Recently I've looked into making it Python 3 compatible, which
> requires changes to both dokuwikixmlrpc and dokuvimki.
>
> Could you give me access (with this email address) to the
> dokuwikixmlrpc package on PyPI so I can push a new release?
>
> [...]
>
> Cheers,
> Florian

I would like to claim the project name otter on PyPI. My project is here, I'm just starting development.

the pypi page gives 404 but I believe there is an existing project with no uploads. I am unable to upload to upload.pypi.org but I am able to upload to test.pypi.org. Similar to pypi/warehouse#5503

Thanks

Hi,

I would like to ask for the transfer of the name apischema. I don't know what is this project as I can not find it on PyPi (so I'm not able to reach the owner), and it cannot be installed with Pip.

Thank you,
Joseph

I tried emailing @xiaoxu193 back in January (7 months ago) and got no response. My Python 3 support pull request has been open since that time as well and there's no activity on Github. Last release on PyPI was in 2015.

I'd like to take over maintenance of this package.

I am unable to reach the maintainer for PyFIT, as the email ([email protected]) bounced back stating it doesn't exist. The package was last updated over 10 years ago. There does not appear to be a GitHub repository associated with the project. Therefore, it can be considered abandoned according to the guidelines. Can someone please transfer ownership to me for use in my project?

https://pypi.org/project/PyFIT/

Referencing issue
pypi/warehouse#1506

Abandonment criteria met:

1. owner not reachable (see Reachability above);
2. no releases within the past twelve months; and
3. no activity from the owner on the project's home page (or no home page listed).

An abandoned project can be transferred to a new owner for purposes of reusing the name when ALL of the following are met:

1. the project has been determined abandoned by the rules described above;
2. the candidate is able to demonstrate their own failed attempts to contact the existing owner;
3. the candidate is able to demonstrate that the project suggested to reuse the name already exists and meets notability requirements;
4. the candidate is able to demonstrate why a fork under a different name is not an acceptable workaround;
5. download statistics on the Package Index for the existing package indicate project is not being used; and
6. the maintainers of the Package Index don't have any additional reservations.

Hello,

As documented in Whoosh pypa/warehouse#544, the original author of Whoosh, @mchaput, appears to have abandoned the project.

1. The last PyPI release was in April 2016.
2. Last commit by @mchaput on his Github repo was in 2015.
3. Last edit to the home page Wiki by Matt was in 2013.
4. There have been various calls out to Matt from Bitbucket and this project's issues but he appears to have been unresponsive to Whoosh for about 2 years.
5. Various announcements [1][2] have to be made steering people from Bitbucket to Github whoosh-community (see below) in order to get attention.
6. I emailed @mchaput at [email protected] on 7/7/2019 but have not received a response.

Meanwhile, a group of engineers dedicated to keeping the project active have moved the code and all associated issues to Github at whoosh-community/whoosh. This community has since been actively fixing bugs for years. This version of Whoosh is significantly improved over the official PyPI release, but the project does not have authority to publish newer releases to PyPI. We are eager to continue releasing newer versions of Whoosh through PyPI.

We are therefore requesting formal transfer of ownership of Whoosh to whoosh-community/whoosh.

I originally made this claim request almost a year ago in pypi-legacy: https://github.com/pypa/pypi-legacy/issues/789 -- That claim was never resolved and has since been archived, and now that PEP 541 is official, I wanted to give this another try.

I would like to claim the name looper for my project. The current looper package on pypi has only one release and the code hasn't been updated in 5 years: https://github.com/CryptoPunk/looper

I have e-mailed the author and started an issue on GitHub but have not received a response from the original author in almost a year. The author is not reachable and I believe the lack of updates fill the requirements for abandonment in PEP 541. In fact it also borders on being an invalid project due to lack of utility ('name squatting'), and only 1 release.

I would like to use the pypi name looper for my existing project, (https://github.com/pepkit/looper) which has been under development for several years and is actively used at several research institutions. It would be nice to distribute this via pypi under the existing name. It is not practical to change the name due to widespread use. How can I go about claiming the name?

Request

I'd like to transfer the ownership of the abandoned spotipy package (PyPI package and GitHub repository) to myself (PyPI account and GitHub repository).

Rationale

The package is abandoned

There is no description on the PyPI page. The most recent commit on the GitHub repository is from Oct 2017. In addition, the version on PyPI is an outdated one (Jan 2017), the repository has code that has not been released. There are numerious issues on the repository asking about the outdated version and the project's state. Moreover, the author's PyPI email is not valid anymore.

The package is still being used

According to pypistats it's pulling in 500 or so downloads per day, even though with respect to the Spotify Web API, which it is a client of, it is outdated. As the repository has advanced with no releases, the documentation is out of sync, which was confusing for me as well when using the library. So thousands of users are downloading a rather obsolete version of the client.

Let me know if there's any additional information you need or if there are further preconditions that need to be met before the transfer is possible!

CC: @jamadden because it seems you have been eager to help in a number of these requests already! And a desparate, final ping to @plamere, the owner of the package :(

In order to publish the ROCm-enabled PyTorch wheel, we need a file size limit bump (current wheel size is 231 MB, so 300 MB would be good. ROCm is AMD's open source heterogeneous computing stack.

Link to project: PyTorch for ROCm

This request would apply to both testpypi and regular pypi.

No prior upload of the wheel.

Thanks!

Describe the bug

I have a release named . that I can't view or delete.

This may or may not be a dupe of #55

Expected behavior

I'm not sure how it got there in the first place, but there's a release named . for one of my projects. I'd like to delete it but I can't. When I try to delete it, I see a 404. When I try to view it, it redirects to the project home page.

To Reproduce
https://pypi.org/project/pymacaroons/#history (scroll to the bottom)

Hi, my understanding is that if we believe that a project is abandoned by the rules of PEP 541, the current process is to post an issue here, since there is no other process at pypi.org. If that's wrong, please let me know and I'll close this.

The package has a merge request to fix linux executable since april

jayjiahua/phantomjs-bin-pip#2

I'm proposing myself as a candidate to continue maintenance on the abandoned project 'gwebsockets'. The original repository is here.

I've tried to contact Daniel Narvaez at last known mail address for several years since 2014, but there has been no answer.

I've supervised porting of the project to Python 3 as release manager for Sugar Labs. The fork of the repository is here.

A fork under a different name is possible, but unwelcome because downstream distributions have referenced the PyPi project. gwebsockets is used by the Sugar learning environment to provide an API to the UI shell for use by JavaScript apps.

Daniel went missing and we never found out what happened. ☹️

Please determine the project is abandoned, thanks.

I would like to increase the size of my pypi repository from 60MB to 120MB (https://pypi.org/project/MAMEToolkit/#files). I have already filed a issue, and was told to make the relevant changes: pypi/warehouse#6197.

I have now made the changes, so I would like to request the file size limit to be increased.

I'd like to request ownership of the dissect package name to be transferred to the PyPI user fox-it. I can provide proof of ownership of this user if necessary.

The last release on PyPI for dissect was on Jul 5, 2015, with the last activity on the GitHub repository on Mar 6, 2017. I've tried contacting the owner multiple times on various e-mail addresses and publicly on Twitter, but without success. Maybe a reach-out from PyPA is successful.

The reason for wanting this package name is that we (Fox-IT) have been building a lot of internal libraries under the dissect "namespace". When we started, this package didn't exist yet and we had no intentions of open-sourcing at the time. However, we're now in the process of preparing to open-source various projects under this namespace (for example, dissect.cstruct).

I'm aware it's a single package right now, but we have multiple projects in the pipeline to be open-sourced. However, not controlling the dissect package on PyPI is somewhat of a show stopper for us publishing more libraries under this name. Since the current dissect package on PyPI hasn't been updated in a long time, we're first attempting it this way before we have to go and think of a different name.

I can provide more information on request, if necessary.

Hi, I, @inducer, would like to transfer ownership of the name "loopy" to myself. The current PyPI package is a package that was first released in 2007 and had two more releases in 2009. It is an abstraction over various main loops (libevent etc). It does not declare a web page, and I was not able to locate a repo. It describes itself as "alpha", and I was not able to find evidence of further development.

I tried contacting the owner (Ariel de Ocampo) in 2013 to ask whether he might be willing to transfer the project, and I received no response.

Andreas Kloeckner <[email protected]> (2013-05-02) (sent)
Subject: "loopy" on the package index
To: arieldeocampo@XXX
Date: Thu, 02 May 2013 19:15:59 -0400

Hi Ariel,

I've been working on a package I've named 'loopy' for quite a while, see
here:

http://iliketoast:[email protected]/loopy
http://git.tiker.net/loopy.git

and I'm getting ready to release it pretty soon. As I was trying to
register the name on the Python package index, I saw that you have an
event loop package called 'Loopy' on there. From the version history,
the project looks a bit abandoned, and I was therefore wondering if you
might be willing to let me have the 'loopy' name. I've used it in a few
conference presentations, and I even have a logo:

http://tiker.net/tmp/loopy.svg

That's why I'd really like to keep the name. If you were to agree, I'd
be happy to link to your project in my project description.

If you're doubting whether I'll make good use of the name, here are
links to a few packages that I already maintain:

https://pypi.python.org/pypi/pudb
https://pypi.python.org/pypi/pyopencl
https://pypi.python.org/pypi/pycuda

I'd really be super-happy if you were willing to consider this.

Thanks!
Andreas

My proposed use of the name would be the project currently available at

https://pypi.org/project/loo.py/

with a Github repository at

https://github.com/inducer/loopy (200-ish stars, 34 forks)

"My" loopy has an active user base, the most prominent of which is likely https://firedrakeproject.org/, with development mostly taking place on my Gitlab instance.

The original loopy represents a not-insignificant amount of code (23 kB tarball), at the same time it looks unused and pretty dead. I would of course be happy to take over the name, but I am also happy to be told "no", or "too soon".

References pypi/warehouse#1506

The existing pyquant package (https://pypi.org/project/pyquant/) is completely devoid of functionality (has no python code), nor any email to contact the existing owner. It has been like this since 2015.

I am the developer of a scientific python package named PyQuant (https://www.ncbi.nlm.nih.gov/pubmed/27231314 and https://github.com/Chris7/pyquant), I would like to distribute under pyquant instead of the existing pyquant-ms. My username for pypi is chris7.

I'd like to apply to take ownership of the project name "slack-cleaner" https://pypi.org/project/slack-cleaner/

Reachability

I tried to reach the original author via email ([email protected]) twice or by filing a issue on the repos github repository (kfei/slack-cleaner#51). However, no response to either of it.

Abandoned projects

A project is considered abandoned when ALL of the following are met:

• owner not reachable (see Reachability above);
• no releases within the past twelve months; and
• no activity from the owner on the project's home page (or no home page listed).

All other projects are considered active.

Continued maintenance of an abandoned project

If a candidate appears willing to continue maintenance on an abandoned project, ownership of the name is transferred when ALL of the following are met:

• the project has been determined abandoned by the rules described above;
• the candidate is able to demonstrate their own failed attempts to contact the existing owner;

-> see github issue among others

• the candidate is able to demonstrate improvements made on the candidate's own fork of the project;

-> my fork: https://github.com/sgratzl/slack-cleaner contains all open Pull Requests added some new features

• the candidate is able to demonstrate why a fork under a different name is not an acceptable workaround; and

a lot of people (as indicated by the stars of the original and the fork project) use the project and encounter the same errors again when installing from pypi since they are stuck to the old version. Thus, being able to update the package with the forked version would simplify things a lot and avoid that the same error is reported multiple times since already fixed in the improved version.

cheers

sam

Hi,
The eccodes PyPi repo (https://pypi.org/project/eccodes/) is limited, out-of-date and the documentation is missing. We tried to contact user "hcsoftcn" - but there are no contact details and we failed to make contact.

ECMWF develops the ecCodes software and we maintain successfully other PyPi repos. We already receive bug/feature reports for this repo, but are not able to fix these. If we could be added as maintainer we will take an active role to support the ecCodes repo and add the missing parts.

Could I please be added as maintainer?

For PEP 541, perhaps we could suggest that every account has to be associated with a valid email address?

Thanks
Stephan

Hello,

I would like to claim the following package:
https://pypi.org/project/keyring-vault-backend/

I opened a PR long time ago with no answer
I tried to contact @pschmitt by email specify in the setup.py with no success

For reference:
Owner Pypi package: keyring-vault-backend
Owner Pypi username: pschmitt
My Pypi username: jynolen

Thank you

Now that PEP 541 has been accepted, there is a formal process for package index name reassignments. However, I couldn't find any information about where to submit these requests. I've seen lots of package-claim requests here, so I am adding this here, but if this is not the right place, can you please direct me to it?

I would like to claim the name looper for my project. The current looper package on pypi has only one release and the code hasn't been updated in 4 years: https://github.com/CryptoPunk/looper

I have e-mailed the author and started an issue on GitHub but have not received a response from the original author in over a month. The author is not reachable and I believe the lack of updates fill the requirements for abandonment in PEP 541.

I would like to use the pypi name looper for my existing project, (https://github.com/pepkit/looper) which has been under development for several years and is actively used at several research institutions. It would be nice to distribute this via pypi. How can I go about claiming the name?

I am unable to reach the maintainer for easyconfig who basically is name-squatting easyconfig.

Referencing issue pypi/warehouse#1506

Abandonment/name-squatting criteria met:

• owner not reachable: tried to contact via pypi mail and github mail
• no releases within the past twelve months - there is only one release from 2014
• project's home page does not exist
• the module has no functionality except for a dict/filewrapper.

I have developed a module which provides dataclass like configuration with yml files I would like to publish under easyconfig. My PyPi name is spaceman_spiff.

Hi all
My project depends on pytorch C++ so file,
I tried some ways to reduce the size needed by cut my project to several small sub-project

But one pytorch .so file is more than 200MB, and is more than 60MB after compress.
Although it is possible to cut one .so file into parts, and then join parts of the .so file to the original,
But this will be cause many trouble

So I need increase the space size to 100MB,
my project name is libtorch at https://pypi.org/project/libtorch/

thanks

I've had a PEP 541 transfer request open on the old issue tracker for over a year.

https://sourceforge.net/p/pypi/support-requests/801/

I'd like to take ownership of the pypi rocketchat package

https://pypi.python.org/pypi/rocketchat/0.1

I believe this project is both abandoned and invalid. The links in the pypi project are broken, but I believe this is the project page.

github - https://github.com/SKantar/rocketchat-api

The project appears to be almost a direct copy/paste of an old version of this project

pypi - https://pypi.python.org/pypi/rocket-python/1.2.2
github - https://github.com/dstegelman/rocket-python

However, the lone source distribution on pypi is broken and unusable (it only contains about half the code in the original project) and has no functionality (hence my claim of an invalid project)

Here are my unsuccessful attempts to contact who I think may be the project owner

SKantar/rocketchat-api#1

Here is the project page and the pypi account that I would like the pypi package transferred to

pypi Account: bpabel
github - https://github.com/bpabel/rocketchat

I'd like to request that the hip project on PyPI be transferred to PyPI user njs.

The hip project was registered in 2013 by user "jgors", and has never had a release or any description: https://pypi.org/project/hip/

According to PEP 541, this is "name squatting", and automatically eligible for a transfer. In addition, I've tried to contact jgors via their gmail address on 2019-09-07 and 2019-09-15, through their darthmouth email address on 2019-09-15, and through github on 2019-09-13, and haven't received any responses.

I would like to claim the project name confu on PyPI our package https://github.com/20c/confu.

The current package looks like an abandoned alpha and hasn't been updated in 4 years:

https://pypi.org/project/confu/
https://github.com/neithere/confu

I emailed the author @neithere about 9 months ago and still haven't heard a response.

Thanks

I'd like to apply to take ownership of the project name "dockenv", for use as a different tool. Following the pep:

• The project hasn't had an update since 2017
• The owner left no email in any of the releases or account
• The homepage url goes to a page that 404s
• The owner has had no activity since 2017 on pypi
• Download status appear to be around 44 for the last month.

The tool I maintain of the same name is here: https://dockenv.readthedocs.io/en/latest/
It has been presented at a security conference, I actively maintain it, and there is interest in the tool from others.

Hi. I'm requesting a size limit increase of the PyPI package CamAi's wheels to 300MiB. The most trimmed down version stands at 260MiB right now, and once a few features are enabled in the near future, it will go to 450MB. Ideally it would be good to have the limit at 500MiB to avoid another request in the next few months.

The CamAi package uses deep learned models to do security and event monitoring on premises with complete control and ownership without having to rely on a cloud based service. Instead of of motion detection it uses object detection (people, cars, bicycles) as the baseline and recognizes instances of each (people by face, cars by position etc.) In order to do these, it has to use deep learned model files, including..

Object Instance detection models 
Face recognition models
Other instance detection models.

It would be great to be able to make this 100% python package available via the most intuitive distribution mechanism possible instead of requiring separate hosting and downloads.

Thank you!

Hey all!

I'd like to use the package name 'fashion' for a new FaaS library I'm working on, but it looks like it is squatted (registered by a user who's email doesn't work, no other packages, no code submitted), can you please make it available so that I can register a package there?

This is my PyPI: https://pypi.org/user/miserlou/
This is the name I'd like to use: https://pypi.org/project/fashion/

There is no code or license or working homepage or working contact information, so I don't think this should be too much of a problem. Otherwise, I'll have to come up with another pun for "faas" but I'd rather not call my project "faascist" or "faascile"!

Thanks!

I have an account "jmunroe" that is associated with the now non-existent email address "[email protected]". Could the email be changed to "[email protected]" so that I can reset the password and regain access to this account? Thank you.

As discussed in pypi/warehouse#1506 , I'd like to ask you to transfer the ownership of https://pypi.org/project/pycryptopan/ to me. As written in pypi/warehouse#1506 the co-author of the code behind pycryptopan is unfortunately deceased. I have git admin and commit privs to the underlying gitub repo (https://github.com/FFM/pycryptopan) but not access to the pypi account. Hence I can't update the pypi page. However, I am continuing to maintain the pycryptopan project.

If needed, I can organise formal proof (certificates of death, written statements of the relatives that I may continue with the pypi page in the deceased' name).

Please advise on the neccessary steps.
Thanks,
aaron.

Hi all
My project is tr (https://pypi.org/project/tr/)
it is a deep learning based OCR system which include many .so files and big deep learning model parameter files(for text line detection and text recognition),
I want a size around 200Mb to store so many files, Thanks

We @nvictus and @golobor would like to transfer the name of the abandoned project cooltools to both of us.

There is no email associated with the author on the Package Index, no documentation on the Index, and the listed Home Page (GitHub repo) has either been deleted or is publicly inaccessible. The source distribution and Github account do list a single gmail address ([email protected]). We have attempted to contact @rtansf several times (by email and LinkedIn) with no response.

We are part of a research lab at MIT working on genome organization. Our project, called cooltools, was created before cooltools appeared on the Package Index. It is a package of tools for analyzing specialized genomic data stored in files with the extension “.cool”, following a tradition in bioinformatics of "file extension" + tools: e.g., samtools, vcftools, bedtools. Already, several colleagues have contacted us for troubleshooting because they pip-installed the cooltools on PyPI by accident.

Because we have not been able to reach the author, no releases have been made in over a year, and the listed homepage is unavailable, the cooltools project currently on the Package Index appears to be abandoned. The download statistics on the Package Index for the existing package indicate that project is not being used -- indeed a number of those downloads were intended to be for our package.

Thank you for considering our request.

I would like to request a transfer of the Mosek project to https://pypi.org/user/mosek/.

I have not found a way to contact the listed maintainer, and the project have only a single release from 2014 (which is a repackaging of the official MOSEK release from back then).

I am currently the official maintainer if the Python interface for Mosek at https://mosek.com (and at github: https://github.com/Mosek), so I would like to be able to start updating the packages regularly.

References pypi/warehouse#1506

@aszekMosek

Describe the bug
I'm the author & maintainer of sysv_ipc. Ten years ago I accidentally uploaded a release that contained the description in the version field, so instead of a standard version string like this --

3.2.1

the version is this --

Sysv_ipc gives Python programs access to System V semaphores, shared memory 
and message queues. Most (all?) Unixes (including OS X) support System V IPC. 
Windows+Cygwin 1.7 might also work. 

Sample code is included.

This extension is released under the GPL. 

You might also be interested in the similar POSIX IPC module at:
http://semanchuk.com/philip/posix_ipc/

Apparently this mess I created causes problems for some automated tools and I would like to delete this one release. (The sysv_ipc package as a whole is fine, I just want to delete this one release.) However, deleting the release requires me to enter the version for confirmation, and I can't seem to enter the multi-line version into the single-line text field, even via copy&paste.

Expected behavior
To be able to delete this release

To Reproduce

1. Go to https://pypi.org/manage/project/sysv-ipc/releases/#modal-close
2. Try to delete the release with the ridiculous version string

Pillow is a fork of the Python Imaging Library, PIL.

Pillow is installed as pip install pillow but imported as from PIL import Image. This mismatch causes confusion for users, this Stack Overflow question and this Stack Overflow question have each been viewed half a million times, and there are a couple other questions caused by this situation. It's a popular library and used by beginners.

On PyPI, the last release of PIL was on Dec 3, 2006 https://pypi.org/project/PIL/#history whereas Pillow is still being actively devolped. This predates Python 3 (2008). Because it predates Python 3, it would okay to transfer the pip install pil name to the authors of Pillow using PEP 541. If not right now, definitely when Python 2 is deprecated in January 2020.