I am new at pyramid framework and I recently started to play with it. However, I'm a bit confused about how a tarball created with 'sdist' gets installed in a production virtual environment. My scenario is as follows:

After finishing a project I created in pyramid called 'myapp', I run: python setup.py sdist in order to create the distribution tarball.
The tarball gets created under 'dist' folder and it contains all my project sources as well as the .ini files (development and production).
I then create a new production virtual environment by executing: virtualenv --no-site-packages envprod
To install the 'myapp' distribution tarball I execute: envprod/bin/easy_install src/myapp/dist/myapp0-0.tar.gz.
It then starts to download and install all the requirements for the project and it also installs the sources of my application under envprod/lib/python2.7/site-packages/myapp

The problem is that neither development.ini nor production.ini are installed in the new prod environment so I have no way to execute 'pserve' since it needs the .ini file.
Am I doing something wrong? Or is there a way to start serving 'myapp' without the .ini files?
Thanks!
As stated by Mikhail, code and configuration are note the same. 
You may want to deploy your package manytimes and not to overwrite already installed configuration and data.
Please note that the db, if present and on file system (sqlite), is not distributed inside the package as well. I guess it's done to allow you to update the code easily.
If your intent is to deploy the package in production environment all you need to do is to copy both the ini you want to use and the database (if sqlite) or to run the initilize_db script (that is installed in bin) before starting the app.
Note that it's always a good idea to test the production ini in a non production environment to be sure that settings are good for you, in particular about logging, because you'll have no console logging.
Though it's good enough for dev/prod environment, it may be a problem for distribution to 3rd party. 
I'm just trying to address similar problems and I think that the main point is to properly configure setup.py and MANIFEST.in, to include what you need in the egg and properly extract them when installing. 
The problem seems to be that easy_install skip all files outside your app folder (so ini files, that are one dir back).
A workaround for that, is to skip easy_install, and just untaz your tarball and then enter your project folder and use:
  pip install -e . --pre
(the --pre is only required if you included pre-release package in your project, maybe because they are a dependency of formalchemy, as I did).
This seems the easiest way toi distribute to other people.
You may want to create the database somehow, anyway, to have it work, unless you include it in the distribution explicitly adding it to MANIFEST file.
Deploy a pyramid application with sdist