On 20/05/2020 4:17 pm, Derek wrote:
Yes - short answer is you cannot really "protect" Python code directly (see: https://python-compiler.com/post/how-to-distribute-python-program )

Long answer - don't sell your code to anyone that you do not trust with it.  Obviously, there is a legal route, but there is also the "name and shame" option.  Sometimes open source is better; you get paid for your time to work on the code rather than trying to sell it as a product - which then you have to try and protect.  The open source option prevents the company from "selling" the code (well, they would look very silly if they tried to do that) and establishes you as the "go to" person for creating and maintaining that type of system. If they do make changes to the open source code, you'd get the benefit as well.

In general, try and create partnerships with your clients so they want to include you in the development process, rather than treating each as other as competitors.


On Tuesday, 19 May 2020 15:22:13 UTC+2, Andréas Kühne wrote:

    You can't really do that with Python - however - IF you want to go
    down that route, you can just use the pyc files - you can
    theoretically backwards compile them, but I think this is the most
    you can do....

    Regards,

    Andréas


    Den tis 19 maj 2020 kl 03:36 skrev Sunday Iyanu Ajayi
    <sunne...@gmail.com <javascript:>>:

        I get your point but my solution is kind of a  SaaS
        Application. the client wants to host it on his controlled
        server  and if they get the source code, they can replicate,
        modify and maybe sell it.  Is there a way to host the compiled
        file or lock the directory to the project.


Maybe you need to discuss the client's requirements and license them to do what you agree is OK and you retain whatever control over the source you want.

I'm guessing that might be expensive getting a lawyer to do it.

Otherwise, as Andréas said, just deploy the pyc files.

Mike

        *AJAYI Sunday *
        (+234) 806 771 5394
        /sunne...@gmail.com <javascript:>/



        On Mon, May 18, 2020 at 9:28 PM Jim Armstrong
        <j...@jimwritescode.com <javascript:>> wrote:

            When I work on client projects, I deploy to a test server
            that is under my control. Once the project is complete and
            they have paid the invoice, I deploy to the production
            server under their control. At that point, I don't care if
            they have access to the code - my contracts give the
            clients all rights to the project code upon completion of
            the project.


            On Friday, May 15, 2020 at 9:22:33 AM UTC-4, Sunday Iyanu
            Ajayi wrote:

                I am working for a client that wants to deploy a
                project I am working on in a remote server and I will
                like to project my source code when deployed so that
                they will not be able to mess with it.

                How can  I  go about it please?

                *AJAYI Sunday *
                (+234) 806 771 5394
                /sunne...@gmail.com/

-- You received this message because you are subscribed to
            the Google Groups "Django users" group.
            To unsubscribe from this group and stop receiving emails
            from it, send an email to django...@googlegroups.com
            <javascript:>.
            To view this discussion on the web visit
            
https://groups.google.com/d/msgid/django-users/636f0636-30df-4ce2-8629-2be8b208ec37%40googlegroups.com
            
<https://groups.google.com/d/msgid/django-users/636f0636-30df-4ce2-8629-2be8b208ec37%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- You received this message because you are subscribed to the
        Google Groups "Django users" group.
        To unsubscribe from this group and stop receiving emails from
        it, send an email to django...@googlegroups.com <javascript:>.
        To view this discussion on the web visit
        
https://groups.google.com/d/msgid/django-users/CAKYSAw3Hqjuz5rD_AsZ5Wa%2B3WBzQ9LN0GzZKHx3D-irztJ1G0A%40mail.gmail.com
        
<https://groups.google.com/d/msgid/django-users/CAKYSAw3Hqjuz5rD_AsZ5Wa%2B3WBzQ9LN0GzZKHx3D-irztJ1G0A%40mail.gmail.com?utm_medium=email&utm_source=footer>.

--
You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com <mailto:django-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/021a40fa-a755-4d77-addf-dfd112597dbc%40googlegroups.com <https://groups.google.com/d/msgid/django-users/021a40fa-a755-4d77-addf-dfd112597dbc%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/4ec2a50a-f08c-b49e-c51b-9068a564ef46%40dewhirst.com.au.

Reply via email to