Ok, let's keep icontract as it was already referenced a couple of times at
least on this list.
I'll rename the pypi package to icontract2 and the module as well as soon
as I change the interface.
On Mon, 1 Oct 2018 at 20:43, James Lu wrote:
> I think the confusion would be minimal and not
I think the confusion would be minimal and not worth the hassle of renaming to
pcontract. People would just say “Python icontract” when it’s ambiguous.
Sent from my iPhone
> On Oct 1, 2018, at 3:28 AM, Marko Ristin-Kaufmann
> wrote:
>
> Hi Cameron,
> A nerdy way to make it sound like a
Hi Cameron,
A nerdy way to make it sound like a sentence: "I contract that ...".
Pcontract would stand for python contract. Pycontract is already taken.
Cheers,
Marko
Le lun. 1 oct. 2018 à 09:15, Cameron Simpson a écrit :
> On 01Oct2018 07:25, Marko Ristin-Kaufmann wrote:
> >I'd like to
On 01Oct2018 07:25, Marko Ristin-Kaufmann wrote:
I'd like to rename icontract into pcontract to avoid name conflict with
java's icontract library.
Do you have any better suggestion?
No, sounds ok to me. What was the "i" for in the old name?
Cheers,
Cameron Simpson
Hi,
I'd like to rename icontract into pcontract to avoid name conflict with
java's icontract library.
Do you have any better suggestion?
Thanks!
Marko
___
Python-ideas mailing list
Python-ideas@python.org
