Visual-studio – Setting the manufacturer in a VS 2008 Setup Project

There are two types of site-packages directories, global and per user.

1. Global site-packages ("dist-packages") directories are listed in sys.path when you run:

   python -m site
   

   For a more concise list run getsitepackages from the site module in Python code:

   python -c 'import site; print(site.getsitepackages())'
   

   Note: With virtualenvs getsitepackages is not available, sys.path from above will list the virtualenv's site-packages directory correctly, though. In Python 3, you may use the sysconfig module instead:

   python3 -c 'import sysconfig; print(sysconfig.get_paths()["purelib"])'
   

2. The per user site-packages directory (PEP 370) is where Python installs your local packages:

   python -m site --user-site
   

   If this points to a non-existing directory check the exit status of Python and see python -m site --help for explanations.

   Hint: Running pip list --user or pip freeze --user gives you a list of all installed per user site-packages.

Practical Tips

• <package>.__path__ lets you identify the location(s) of a specific package: (details)

  $ python -c "import setuptools as _; print(_.__path__)"
  ['/usr/lib/python2.7/dist-packages/setuptools']
  

• <module>.__file__ lets you identify the location of a specific module: (difference)

  $ python3 -c "import os as _; print(_.__file__)"
  /usr/lib/python3.6/os.py
  

• Run pip show <package> to show Debian-style package information:

  $ pip show pytest
  Name: pytest
  Version: 3.8.2
  Summary: pytest: simple powerful testing with Python
  Home-page: https://docs.pytest.org/en/latest/
  Author: Holger Krekel, Bruno Oliveira, Ronny Pfannschmidt, Floris Bruynooghe, Brianna Laugher, Florian Bruhin and others
  Author-email: None
  License: MIT license
  Location: /home/peter/.local/lib/python3.4/site-packages
  Requires: more-itertools, atomicwrites, setuptools, attrs, pathlib2, six, py, pluggy
  

• None: The file is not included in the project output group and is not compiled in the build process. An example is a text file that contains documentation, such as a Readme file.

• Compile: The file is compiled into the build output. This setting is used for code files.

• Content: Allows you to retrieve a file (in the same directory as the assembly) as a stream via Application.GetContentStream(URI). For this method to work, it needs a AssemblyAssociatedContentFile custom attribute which Visual Studio graciously adds when you mark a file as "Content"

• Embedded resource: Embeds the file in an exclusive assembly manifest resource.

• Resource (WPF only): Embeds the file in a shared (by all files in the assembly with similar setting) assembly manifest resource named AppName.g.resources.

• Page (WPF only): Used to compile a xaml file into baml. The baml is then embedded with the same technique as Resource (i.e. available as `AppName.g.resources)

• ApplicationDefinition (WPF only): Mark the XAML/class file that defines your application. You specify the code-behind with the x:Class="Namespace.ClassName" and set the startup form/page with StartupUri="Window1.xaml"

• SplashScreen (WPF only): An image that is marked as SplashScreen is shown automatically when an WPF application loads, and then fades

• DesignData: Compiles XAML viewmodels so that usercontrols can be previewed with sample data in Visual Studio (uses mock types)

• DesignDataWithDesignTimeCreatableTypes: Compiles XAML viewmodels so that usercontrols can be previewed with sample data in Visual Studio (uses actual types)

• EntityDeploy: (Entity Framework): used to deploy the Entity Framework artifacts

• CodeAnalysisDictionary: An XML file containing custom word dictionary for spelling rules