Am 14.04.2016 um 14:31 schrieb Ian Cordasco:
On Apr 14, 2016 2:20 AM, "Thomas Güttler" mailto:guettl...@thomas-guettler.de>> wrote:
>
> I think it would be very cool if you could install a package editable
> without the repo-url.
>
> The default repo-url can be defined in the meta-data of
Am 14.04.2016 um 20:50 schrieb John Wong:
On Apr 14, 2016 2:20 AM, "Thomas Güttler" mailto:guettl...@thomas-guettler.de>> wrote:
> Next use case: you use software third-party-foo-lib in your project.
> Up to now you use it as package. You find a bug and want to fix it.
> Wouldn
To my knowledge, metadata 2.0 does not have any reliable means to
specify a repository URL.
So how do you propose to retrieve this information?
15.04.2016, 13:05, Thomas Güttler kirjoitti:
Am 14.04.2016 um 14:31 schrieb Ian Cordasco:
On Apr 14, 2016 2:20 AM, "Thomas Güttler"
mailto:guettl.
On Apr 14, 2016 11:52 PM, "Luís de Sousa" wrote:
>
> Hi Marius, thank you for the reply.
>
> If I remove the line # coding=utf8, I get the following error:
>
> $ python setup.py bdist_wheel --universal
> File "setup.py", line 18
> SyntaxError: Non-ASCII character '\xc3' in file setup.py on line
If you get that error, it means you're not actually using python 3 to
run setup.py.
15.04.2016, 09:52, Luís de Sousa via Distutils-SIG kirjoitti:
Hi Marius, thank you for the reply.
If I remove the line # coding=utf8, I get the following error:
$ python setup.py bdist_wheel --universal
Fil
Brett suggested I ask the kind folks here.
As you may or may not know, there's an old unmaintained "mypy" package on
PyPI that attracts a fair amount of downloads from people trying to
download mypy the type checker. We then get bug reports and have to explain
in our tracker that they have to use
I've fallen into this trap as well, so +1 for the takeover.
It might be a good idea to come up with a standardized process for
taking over old, unmaintained packages.
16.04.2016, 02:29, Guido van Rossum kirjoitti:
Brett suggested I ask the kind folks here.
As you may or may not know, there's
Hi Guido,
Because this sort of thing has come up a lot in the past, and because I've
copped trouble for mishandling it in the past, I took the trouble of
writing up a formal description of how I handle these sorts of issues:
https://docs.google.com/document/d/1elum7ENjQb0dLB4ATfYNtnXYVLUzsKacc0VW
Why are you so determined to use the name "mypy" in the
first place? Seems to me it's a terrible name. It sounds
more like a working title for someone's personal
implementation of Python, and certainly gives no clue
that it has anything to do with type checking.
So instead of trying to steal the
Oh well. I wonder if offering money would change the situation.
On Fri, Apr 15, 2016 at 5:10 PM, Richard Jones wrote:
> Hi Guido,
>
> Because this sort of thing has come up a lot in the past, and because I've
> copped trouble for mishandling it in the past, I took the trouble of
> writing up a f
Another thing. Is the search index on pypi.python.org no longer being
updated? Searching for mypy-lang still takes you to mypy-lang 0.2.0, even
though 0.3.1 has been released many weeks ago. I just updated the typing
package and searching for that still shows the old versions.
On Fri, Apr 15, 2016
On Fri, Apr 15, 2016 at 8:59 PM, Guido van Rossum wrote:
> Another thing. Is the search index on pypi.python.org no longer being
> updated? Searching for mypy-lang still takes you to mypy-lang 0.2.0, even
> though 0.3.1 has been released many weeks ago. I just updated the typing
> package and sear
12 matches
Mail list logo
