On 8/23/12, Ethan Jucovy <[email protected]> wrote:
> On Thu, Aug 23, 2012 at 2:36 PM, Steffen Hoffmann <[email protected]> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Am 22.08.2012 16:23, schrieb Ethan Jucovy:
>> > The plugin is available on PyPI, Github and Bitbucket,
>>
>> Do you have a PiPI primer, something to get me started on this?
>>
>
> Sure.  http://guide.python-distribute.org/quickstart.html is a good start
> (and that site has a lot more detailed information too beyond that page)
>
> The two-second version is:
>
> {{{
> cd /path/to/accountmanager
> python setup.py register sdist upload
> }}}
>

I use to add --formats=gztar,bztar,zip to the command line in order to
ensure all kinds of sdist file types will be uploaded at once . There
is no way to ensure this will happen and if a register command fails
if trying to upload unsupported tarball format .

> That will prompt you to log in to PyPI or create a new account if you've
> never done so before.  It will then send your package's metadata (from
> setup.py) to PyPI; create a tarball with the code; and upload it to PyPI.
>

... ho! I wish that was true ... it's just part of the truth

> Three details to note (now it's the five minute version) --
>
> 1) Permissions.
>
[...]
>
> Alternatively, you can register it
> at a different location like trac-AccountManagerPlugin or whatever.

Please don't , unless it's a last recourse alternative . If coderanger
agreed to delegate that responsibility on you , it's possible he'll
add you @ PyPI as well

>
> 2) Including non-code files.  As Olemis pointed out, you'll need to create
> a file called MANIFEST.in next to setup.py -- this will tell setup.py what
> "non-code" files (htdocs, documentation, etc) to include in the package.  I
> always forget to do this

You didn't forget ... those who designed distutils in first place
managed to figure out what files to distribute within binary
distributions , and deliberately didn't do the same thing for sdist
tarballs , hence forced us since long time ago to specify the same
thing over and over in many different places . The same happens with
install_requires vs requires , etc , etc ... so if you ask me about
distutils ... probably you won't notice a bit of happiness in the
answer

[...]
> There are a lot of ways to write this
> (documentation here:
> http://docs.python.org/distutils/sourcedist.html#the-manifest-in-template)
> but the simplest thing that will probably work is to just add a line like,
> "graft acct_mgr".
>

you have to be carefull because you could include undesired files
(e.g. somehow compiled files) in sdist packages . Use graft statement
carefully , e.g. when you know a folder only contains source files
e.g. htdocs, templates, but select files within locale folder . Even
if I added in the 1min MANIFEST.in file I suggested before , IMO
that's not correct

[...]

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:
Resolviendo el problema 1 de la IMO 2012 con inversión -
http://simelo-es.blogspot.com/2012/08/resolviendo-el-problema-1-de-la-imo.html

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.

Reply via email to