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
On 01Oct2018 07:25, Marko Ristin-Kaufmann <marko.ristin@gmail.com> 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 <cs@cskk.id.au>
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 <cs@cskk.id.au> a écrit :
On 01Oct2018 07:25, Marko Ristin-Kaufmann <marko.ristin@gmail.com> 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 <cs@cskk.id.au> _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
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 <marko.ristin@gmail.com> wrote:
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 <cs@cskk.id.au> a écrit : On 01Oct2018 07:25, Marko Ristin-Kaufmann <marko.ristin@gmail.com> 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 <cs@cskk.id.au> _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
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 <jamtlu@gmail.com> wrote:
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 <marko.ristin@gmail.com> wrote:
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 <cs@cskk.id.au> a écrit :
On 01Oct2018 07:25, Marko Ristin-Kaufmann <marko.ristin@gmail.com> 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 <cs@cskk.id.au> _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
participants (3)
-
Cameron Simpson -
James Lu -
Marko Ristin-Kaufmann